Comments by "TheEvertw" (@TheEvertw) on "The WORST Way to Develop Software" video.

  1. One thing underpinning the Waterfall model is that development happens at many different levels of abstraction. As a person can only grasp a limited spread from high to low abstraction, the steps in Waterfall are often done by different people. The fault in the Waterfall model is that it assumes people working at higher levels of abstraction can predict with 100% confidence the needs for the lower levels and are isolated from any discrepancy. This feels very safe for managers, who are thus isolated from the nitty-gritty details in a project, but is not how the world operates.
    2
  2. I really like your comparison with developing a new method for building a bridge. Many wonder why Software is different from all other technical disciplines in how unpredictable it is. But in actual fact, it isn't different. It is just that people compare SW development with the factory-like production of standard products. Whereas SW development needs to be compared with product development. Just look at the requirements for being a software developer. Most developers have either a Master or Bachelor degree, sometimes even a Doctorate. Like we see in teams that do product development. SW development has little use for people with limited education, people who could happily be employed in a factory.
    1