3 ms·
> 6. Go home and once in a while cook food. YES, real food. It will teach you the difference bet following a recipe and creating a meal While most of the other
by barclay 16y ago
> 6. Go home and once in a while cook food. YES, real food. It will teach you the difference bet following a recipe and creating a meal
While most of the other points we've all heard many times, this one (IMHO) was actually pretty clever. This is something I've been thinking about a lot lately when I'm prepping: the parallels between cooking and writing software (since I do both a lot).
As an developer, it's interesting to look at cooking through the lens of: here's something fairly established you need to build (the dish). You have docs and RFCs (the recipe). You have tools that, while different, could be argued are more or less powerful than your IDE (knives, pans). You can complete the assignment, and get it good enough so all your tests pass (it's edible). You can refactor and tidy things up to make it a little better (seasoning).
Now how do you take it to the next step, from fine to fan-fucking-tastic? Is it the same process as engineering (reading, studying, lots of practice)? Is it just innate?
Anyway. Interesting point. Funny to see someone else is there, too.
- Goladus 16y agoI think the key here, though, that the author didn't mention, is that you should cook some real food for for other people. I can make food that I think is fantastic for myself, but isn't necessarily presentable. I can slop together pasta dish full of random fresh vegetables using homemade tomato sauce. I think it's absolutely delicious, because I don't mind dumping the whole runny mess into a mixing bowl and eating out of that. Either I have to sell that strategy to my guests, or I have to put some more thought into presentation, repeatability (I have to be able to prepare the food on their schedule rather than mine) and probably, more care needs to be taken when choosing the combination of vegetables and spices.