DEV Community

Discussion on: The ONE chart every developer MUST understand

Collapse
 
johannesjo profile image
Johannes Millan

Even though I was pushed back by the clickbaity title, I must admit tat this was a very interesting read. Throughout the years I've experienced a lot of the problems mentioned again and again. The bigger the project the more important it gets to have good conventions about which hopefully everybody is on board, automated tools to assist you on the way, and processes to share knowledge and to allow for reflection and improvement. And while it might work out on a smaller scale, rushing things on big projects is the worst as it tends to backfire many times over.

Collapse
 
bosepchuk profile image
Blaine Osepchuk • Edited

Yes, Johannes, the authors of The Economics of Software Quality repeatedly make the point that larger projects are disproportionately more difficult to manage successfully than smaller projects.

Why do you think people resisted adopting enough process to ensure success on larger projects you've worked on?