> When it comes to writing code, the number one most important skill is how to keep a tangle of features from collapsing under the weight of its own complexity.

> When it comes to writing code, the number one most important skill is how to keep a tangle of features from collapsing under the weight of its own complexity. I've worked on large telecommunications systems, console games, blogging software, a bunch of personal tools, and very rarely is there some tricky data structure or algorithm that casts a looming shadow over everything else. Could not agree more. Most programs require appropriate organization. The Venn diagram intersection between puzzle solvers and organizers is pretty small. The last thing an organizer wants to see in the code is unneeded cleverness. That is, cleverness that is only there because the author is a bored puzzle solver.