While changing requirements/expectations are part of the problem, I find that projects based on increasingly complex technical stacks and frameworks that impede

While changing requirements/expectations are part of the problem, I find that projects based on increasingly complex technical stacks and frameworks that impede functional changes are another. Those bloated technical parts tend to be focused solely on supporting (and providing flexibility for) non-functional requirements. Is it then a surprise that functional changes can't be handled effectively? Perhaps that is because developers really focus on technologies, not how to represent a complex business problem or systems into a model which is represented in code. Representing the business problem in a system, including changing functional requirements seems to be both a lost art, and a forgotten need.