Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To me, a big reason is that people who don't understand how it works have a say in how it should be done.

It's not the case in traditional engineering fields: when you build a dam, the manager cannot say "hmm just use half as much concrete here, it will be faster and nobody will realise". Because people can go to jail for that. The engineers know that they need to make it safe, and the managers know that if the engineers say "it has to be like that for safety", then the manager just accepts it.

In software it's different: nobody is responsible for bad software. Millions of people need to buy a new smartphone because software needs twice as much RAM for no reason? Who cares? So the engineers will be pushed to make what is more profitable: often that's bad software, because users don't have a clue either.

Normal people understand the risks if we talk about a bridge or a dam collapsing. But privacy, security, efficiency, not having to buy a new smartphone every 2 years to load Slack? They have no clue about that. They just want to use what the others use, and they don't want to pay for software.

And when it's not that, it's downright enshittification: users don't have a choice anymore.





Exactly! software is the only engineering discipline where failure has no liability and degradation has no visibility.

Bridges collapse once. Software collapses silently, one abstraction at a time. The incentives are inverted: short-term growth gets rewarded, long-term stability gets deprecated.

When there’s no physical consequence for failure, “good enough” becomes the design philosophy.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: