> Now that dev tools are so good and computers so powerful, spec changes are cheap I‘d like to differ. Changing the spec in every iteration is going to end you

> Now that dev tools are so good and computers so powerful, spec changes are cheap I‘d like to differ. Changing the spec in every iteration is going to end you up with a suboptimal architecture, because at some point devs will stop tearing it all apart and just refactor „a bit“. Of course, that’s different for various project sizes - a mega project like FB obviously has to allow changed requirements, all the time. But I‘m not sure that should actually be called a project. An atomic project should be of finite duration, and it should be finishable. Ideally not longer than 6 months. For those, requirements should not change much after a short cool-down phase. Just like tasks/stories/features/epics, projects are made up of different levels with very different aspects. I find the ideas presented in the article appealing, because they are refreshingly realistic even for one-off freelance projects to pull off.