> That's really a textbook example of software projects going horribly wrong. It's often a good idea to take a step back and analyze whether you're overcomplica

> That's really a textbook example of software projects going horribly wrong. It's often a good idea to take a step back and analyze whether you're overcomplicating things. The question is what to do about it. Simply taking a step back and analyzing is not enough. Most of us have been on the projects that were overcomplicated and knew they were overcomplicated and knew a simpler solution and yet didn't have the power to do anything about it. The ultimate power is to be able to walk away form the project but how many people can afford that? So, I believe the problem is not technical but rather socio-economic. I am not sure how to solve it.