[FLUX-YOU]

> Because that engineer is the one who will prevent the project from collapsing under the weight of scope creep and tech debt.

That's the shitty thing: there's enough work that doesn't cross the threshold that requires you to pay for technical debt. Otherwise, a lot more managers would be getting burned by it. There's no electric shock when they hit the wrong button. Even if it isn't a "big boom" moment where you can't deliver some huge new feature because of bad architecture and lose a lot of potential money, the little payments are written off to the younger generation to actually rebuild the thing because they have energy/time to burn.

[dasil003]

There's not really a single threshold though. I think the shittier thing is that software is just an incredible market for lemons. Even us programmers ourselves don't really know how good we are, and there is no way to accurately compare all the problems we faced with the problems we avoided. So forget about non-technical management, they could be paying twice as much for someone who takes 10x as long to deliver a feature and never have the first hope of getting a clue. Or they could hire someone who is demonstrably fast but paints the whole system into a corner where the next critical business feature requires a complete rewrite.

Experience is no silver bullet, but it generally goes a lot further than non-technical tea-leaf-reading or junior dev shotgun programming.