Agreed, many of those huge and overly complex projects also fail and overrun implementation schedules though, and they only ultimately operate with a ton of wor

Agreed, many of those huge and overly complex projects also fail and overrun implementation schedules though, and they only ultimately operate with a ton of workarounds and shortcuts. I find a lot of projects that barely match original documentation limping along, or just even after a major failure or breach in my line of work, with the customer desperate to find a patch to just keep them running after a bunch of critical data is under siege within apps. A key for me is convincing a customer to simplify goals and implement an MVP on a reliable framework, to plan versions, and to thoroughly test... Makes me a code cop, but there are reasons why these steps are in place for mission critical services, and if a customer wants to skip them and just deploy in careless "Twitter Dev Mode" I have them physically sign paperwork that states their accountability for the bad decision... When individual accountability is mentioned, they usually opt for the more stable & reliable methods of dev. Hah.