Filip Hracek
Aug 22, 2017 · 1 min read

Good point. From which it follows, I think, that the poorer the design (for refactoring), the more likely it is to be pray to full rewrite with yet another “solution to all problems”. So teams with less refactoring / change-management experience are bound to this never-ending circle, while a single well-planned, easy-to-refactor release can speed past these once the first major change is needed.

This brings back to mind this 17-years-old article by Joel Spolsky.

)

    Filip Hracek

    Written by

    Developer and manager working on Google’s Dart programming language and Flutter SDK; gamebooks enthusiast; https://filiph.net