> extremely late integration That's only late if there are other big changes going in at the same time. The vast majority of operational/ticketing issues have

> extremely late integration That's only late if there are other big changes going in at the same time. The vast majority of operational/ticketing issues have few code changes. I'm glad I had the experience of working on a literal waterfall software project in my life (e.g. plan out the next 2 years first, then we "execute" according to a very detailed plan that entire time). Huge patches were common in this workflow, and only caused chaos when many people were working in the same directory/area. Otherwise it was usually easier on testing/integration - only 1 patch to test.