What should I learn next as a programmer?

My point was of a more general nature, for those of us who want to make a long-term career out of programming, and keep getting better at it. A lot of us (myself included) get stuck re-building simple stuff in a newfangled technology every few months and mistake that for progress. If we are to ever get to a place where we have the confidence to build larger and more complex things, we have to try making them, instead of being slaves to the latest project with the most Github stars. It won't be easy, but that is the point of deliberate practice - do something that is slightly beyond our reach and slowly push the bar.

Alton Brown's recipes aren't always my preferred method, but he's an excellent teacher, and great at explaining the science and the "why" behind how cooking works instead of relying on pure folk wisdom like most cooking teaching.

Honestly, if you watch all 10 seasons of Good Eats you'll probably get more out of it than you would a culinary degree from all but a handful of schools.

You don't have to read the heartfelt blog posts if you don't want to, just scroll until you see a recipe.

Note that they all have five ingredients or less (excluding salt & pepper).

They're also all really nice and tasty, as far as I've tried them.

I like this because it sees food as just simple combinations of cooked edible things. You don't have to combine dozens of spices or do anything super fancy.

Just get a chef's knife that doesn't suck. If you want to, look at some videos of chopping techniques, especially for specific tricky things like onions—you can do it so much faster and better with a simple technique, astound your friends!

And do some basic "mise en place," which is just the French word for "preparing your stuff ahead of time even maybe using a few different bowls." If any moment of cooking a meal stresses you out, notice that and think about if you can do it in a way that isn't stressful. Like, if you're suddenly chopping an onion while you're watching garlic in a skillet, you should have prepared all that stuff beforehand.

Be fundamentally nonchalant about measures and times, for almost everything, except in baking. (Rice/water ratios etc are good to follow if you don't want soggy/hard rice.) Recipes say "2 tablespoons" because they need to give some indication, but it will probably be fine if you put in more or less. It's nice if you can look at a recipe, get the gist of it, and then just go with your intuition—if you're wrong, you learn something.

If you really do not know how to start there are always cooking classes. They can be fun, but they are not strictly necessary.

With a little bit of practice you'll realize that you just need to have a few stock ingredients on hand to be able to take care of yourself every day and cook for friends and family.

The feeling you get the first time you cook a meal for someone else is a great one. :)

http://www.amazon.co.uk/Madhur-Jaffreys-Indian-Cookery-Jaffr...

This book, or at least the original, is at least partly responsible for the overwhelming popularity of Indian food in the UK and the ability to find any Indian ingredient you care to mention in any supermarket. It's well written, easy to follow, and her recipes all work.

She was one of the first TV chefs in the UK, and has written a million other books on Asian cooking of all kinds, all of which are just as good, and go into a lot of fascinating historical and cultural background as to just why you're making just what you're making.

A lot of the episodes of her TV series (from 1978!) are on Youtube.

Apart from cooking - which as a few people mention is pretty easy once you realize it's more about common sense and taste than chemistry - the fact the most people think that fat will actually just turn into fat on your body, and that dieting is the way to go, is something I imagine is misrepresenting the importance of being able to put together a healthy and nutricious meal.

Unfortunately, I don't know any good english books on the subject, but I imagine there are plenty of shorter books that will explain how fat, carbs, protein and vitamins play a part in respect to your wellbeing. I would start here.

Next, I would take a look at my wallet and my daily schedule, and figure out when buying take-away is going to be the most realistic option (both in regards to price and context), and when I have the ability to prepare lunch or dinner from home. If you have access to a fridge, a simple lunchbox with carrots and chicken provides a sturdy and surprisingly satisfying meal. Both carrots and chicken can be prepared in large batches, and both holds up for 4-5 days which is a typical workweek. In the morning, you simply fill a box with ingredients, and you have one cheap, nutritious meal down. I usually spice something like this up with a handful of almonds or nuts, and perhaps purchase some milk or juice to go with it.

I don't even know if this makes any sense, but I have this stereotyped view on americans as people who rarely cook their own meals, partly due to the fact that it's cheaper to buy take-away due to lower salaries effect on the price-levels (I can see that being a factor in Europe).

If you've never been comfortable cooking yourself, I can see that this might be a daunting task. I know people who are afraid to cook without a recipe, which is something that I hardly ever bother to spend time finding anyway.

I grew up in a household where everyone cooked, it was (and still is) a massive part of our family. This book was the cornerstone of my 'education' even before I was a teenager. My Mum always had her nose in it. I cannot recommend it enough. It's also worth seeking out some of Delia's cooking shows, there are probably a ton of them on YouTube.

Follow her instruction and you will not go wrong. I guarantee it.

But the tone you set at the beginning is harsh and it does not feel like you spend a lot of time with more experienced developers. They are often so experienced because they didn't stop learning.

And then the whole article has some anecdotal feeling. Everybody had different experiences with different communities, I for myself had the feeling that many researchers at the university often are only interested in their specific topic. While all my programming colleagues did tons of other stuff where they had to learn things like brewing, cooking, playing instruments and so on. But now I work in an environment with researchers from the humanities and they're overly exited about digital research methods and they invest a lot of energy into learning those. On the other hand, the last time I attended a meeting of Nodejs people I saw a presentation about a new cool framework for restful APIs that used experimental features of Nodejs and the presenter stated that he used it while developing a backend for a random client. I'm pretty sure the client would have liked a bit of grumpiness against new frameworks there.

At last, a lot of innovation is driven by big companies. Think about Andrei Alexandrescu and his work at Facebook or Simon Peyton Jones at Microsoft Research (only to name a few).

One of the biggest problems with programmers in general is not their conservatism, but rather the wide variety of opinions that are incompatible. Or, possibly in a less polite way of framing it: programmers are often wrong. One time one of my young colleagues opined that while he was sometimes wrong, there was no way that he could be wrong all the time. I had to think about it a lot, but I realized eventually that, yes, it is actually quite easy to be wrong all the time as a programmer.

You speak very enthusiastically about measuring your success and taking action based on a rigorous scientific approach, but I don't think you will be successful. Or at least, if you are then you are doing something extraordinary and I will very much look forward to your next blog post ;-)

A massive problem in this industry is confirmation bias. That's when we have an idea and we go out looking for evidence that it is correct. If we find said evidence, we often feel vindicated in our beliefs. Unfortunately if we have not also searched for evidence that we are wrong, then we have fallen victim to this bias.

Reading blog posts of people you respect and trying out techniques to see if you agree is fantastic. However, it's also a great way to fall victim to confirmation bias. Soon, you start to see thing coloured one way and people who do not agree seem to be wrong, or at least out of date.

1.5 years is not enough time to be able to form reasonable judgements about whether the application of a technique is good or not. At the very least you need to be able to build a huge code base and let it crumble under its own weight before you can even begin to see the issues involved. Write at least 100,000 lines of code first and then re-evaluate your position. Better to write 500,000 or even a million lines.

I started programming at the age of 9. I'm 48 now. I got my first paying gig at 18 and there have been many, many more days in my life where I have been programming than where I haven't. I can tell you that I'm not holding on to my old techniques with a death grip. It's just that in several decades of being a professional programmer, I know thousands of ways to fail and only a few to succeed.

I sincerely wish you the best in your adventure and I hope you keep the spirit you have now. Just understand that the terrain gets considerably more rocky as you go forward ;-).