4 ms·

Oh, but in what regards programming I fundamentally agree with you. And in what regards cooking, I'd go for an hybrid model as you mentioned, rather than a pure

Oh, but in what regards programming I fundamentally agree with you. And in what regards cooking, I'd go for an hybrid model as you mentioned, rather than a purely declarative one. I got side-tracked by your reference of one of my pet subjects and wasn't at all thinking about your real argument on programming, sorry for that! Coming back to cooking: the best guys won't be much following the recipe but reading between the lines to get to the real information, mostly ignoring the imperative steps (which are usually declinations of techniques they already know by heart). Taking the SQL example: the recipe model gives you something like the result of an EXPLAIN command, often without the benefit of having the actual SQL statement. Sort of.

taeric 13y ago
:) Completely agreed on the best cooks. And no apologies necessary! I feel I owe a giant thank you to all involved in this entire thread. Has been a joy trying to digest all of the facets covered. In this subthread, it comes back to what is the program trying to accomplish? Communicating exacting steps to the computer to perform (as few computers will "ignore imperative steps"[1]), or communicating to the next programmer what was intended. Or both? Seems we both feel it is both, and hence needs a hybrid approach. [1] I realize this isn't even strictly true. Computers are free to reorder some instructions, for example.