4 ms·
I completely share your experience. It almost always takes me two complete drafts before getting an architecture right anyway. This probably looks awful to peop
by thibauts 12y ago
I completely share your experience. It almost always takes me two complete drafts before getting an architecture right anyway. This probably looks awful to people who like to "ship" more than they like to "build". I like to build.
Converging towards the simplest representation of a problem's solution takes a strong ability to let loose on your mental pictures in order to escape local maxima, and time. What we do is essentially rewiring our brains around a problem. In this respect we are bound by biological processes. There is no shortcut. Every path that looks like a shortcut will lead to conceptual pollution that will only grow like the square of the team size and seed what we use to call technical debt.
- jrochkind1 12y agoYes, you said it well. It requires a very thorough understanding of the domain you are working to create a solution in. And time and effort. The actual context most software engineers find themselves in does not usually encourage (or even allow?) that kind of development. Creating quality software really is more 'expensive'.
- thibauts 12y agoYes it tends to be more expensive at first. But look, as a community we can't even (yet) agree on what makes quality. It is hard to sell something you can't clearly explain.