I think it's fair to say that changing requirements coupled with a limited amount of time results in non-incidental complexity. It's a systemic problem that re

I think it's fair to say that changing requirements coupled with a limited amount of time results in non-incidental complexity. It's a systemic problem that results when the entire leadership stack isn't aware of how good software is created. Because of the limited amount of time and resources given, quite often it's a business/management problem. And that's not to say that it isn't also a software dev problem. We've all seen some horrific things. But I've also seen horrific things because there was no one senior there because they wouldn't pay enough for it. it's all intertwined, there's not a simple explanation. But changing requirements is definitely a source of complexity.