[rxm]

Hardy's rule can be adapted to programming: to code it better, think it gooder. One big difference in productivity comes from making good design decisions early on and not taking shortcuts that weeks later turn into spaghetti hacks.

[collyw]

To me this is the most important thing i have learned in 15 years of coding. Its also the reason why I hate interview "tests", I don't come up with a good design straight away. I prefer to get in idea of what is needed, then think about it for a few days while working on other stuff.

[dangravell]

If someone uses interview tests in that way they're doing it wrong.

That's not what interview tests are for; they're for demonstrating a base level of competence and how you think about code during a discussion of the code. Also for acting as a catalyst for more discussion about programming.

[rxm]

You are so right. Good design doesn't just pop out of nowhere. It does emerge early on, but requires work and time while the complexities of the problem are groked.