2 ms·
All software is written three times. First, to learn the problem. Second, to learn the solution. Thrice, to do it right. Skip a step at your own peril. Incre
by specialist 9y ago
All software is written three times.
First, to learn the problem. Second, to learn the solution. Thrice, to do it right.
Skip a step at your own peril.
Incrementalism and do-over both have their place.
If you're resurrecting legacy code, I can't imagine successfully rewriting it until after you understand both the problem and solution. Alternately, change the business (processes), so that the legacy can be retired / mooted.