The difference is, the law says if a contractor signs a contract to do something at x price, they HAVE to do so or suffer consequences. So contractors go broke/bankrupt, lose their licenses, or figure out how to bid correctly enough they can either weasel out of it if it goes sideways or they have enough wiggle room to deal with the inevitable problems.
Software Engineering Consultants have the same situation. But directly employed software engineers are in a different position of course.
One thing that typically makes this worse, is the implicit assumption that planning/quoting/estimating is ‘free’ work, and since it CAN make things easier to deliver, therefore we should do more and more of it as, since it’s free, it will solve the problem no?
And their disciplines involve massive capital outlays which can’t be refactored in a cost effective way, or at all really.
Not defending the ‘no estimate ever’ approach, it doesn’t work. They are different though.
Tell me, how accurate were the estimates for the launch date of JWST?
I’ll wait here while you look up how many times and how many years that “slipped”.
I bet some dumbass NASA manager asked the team to schedule the launch date back in the 1990s.