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.