Earlier quoted context omitted.
OTOH, I was hired by an enterprise that was many months into a giant backend rewrite. After wrapping my head around the many plans, I realized they were rewriting Django, badly. One weekend I prototyped the whole thing… in Django. It worked. It met the specs. It was a CRUD app with a REST API. I came in to work Monday morning, showed it off, and inadvertently triggered a firestorm. Later my boss told me not to do tha…
> Sometimes the new guy can make a better version themselves over the weekend, not because they’re a supergenius, but because they’re not hampered by 47 teams all trying to get their stamp on the project. In 99.9% of cases what seems to be "the better" version is better only for the "new guy" or rather his ego. Those 47 teams hampering doesn't necessarily mean a bad thing, and more often than not actually well justif…
The examples are legion, and they always seem to have NIH and baroque requirements, and be rather over- than underspecified. I would go so far as to say that these projects are almost never successful (and definitely never on time and budget).