Write your code, so that a junior programmer can understand it.
Test it and design it, as if you expect it to fail.
Plan the architecture, as if you were going to have to explain it to financiers.
If you find yourself struggling to hide the complexity, it is too complex.
This is why I don't like frameworks very much... Two sides of the same coin though depending on the application. If the application is big, then a framework can simplify, but if the objective is not that large in scope, a framework just makes things more complicated. I think there area lot of apps out there with frameworks they don't really need. Not that they aren't more performant or extensable this is. They probably are, but it makes I harder for other developers to jump in and contribute.
Too much noise, sometimes.
Isn't this how we should "write" our life as well?
