It's a plausible argument and I do like the idea of having one person write a working app as a skeleton before farming out components to others. It also fits in well with the Agile approach of...
It's a plausible argument and I do like the idea of having one person write a working app as a skeleton before farming out components to others. It also fits in well with the Agile approach of always having a working app to demo and let people try out, and maybe ship, though that's sometimes only in theory.
I also think reusable components work out better when you have multiple real-world usages before factoring out common code.
But this page seems a bit dogmatic in how it's expressed and thin on evidence? Dijkstra wrote a lot of things but it doesn't mean he was always right.
It's a plausible argument and I do like the idea of having one person write a working app as a skeleton before farming out components to others. It also fits in well with the Agile approach of always having a working app to demo and let people try out, and maybe ship, though that's sometimes only in theory.
I also think reusable components work out better when you have multiple real-world usages before factoring out common code.
But this page seems a bit dogmatic in how it's expressed and thin on evidence? Dijkstra wrote a lot of things but it doesn't mean he was always right.