I agree that many issues with bad code could really be avoided by first thinking about the solution a bit, of which the code is just an expression. I'm not adv

I agree that many issues with bad code could really be avoided by first thinking about the solution a bit, of which the code is just an expression. I'm not advocating weeks of architecture astronauting without code feedback - because practical considerations (e.g. the compiler can't deal with this kind of code due to some limitations) matter - but some people seem overeager to just start writing some code "and see what happens".