Post #4300258
2026-08-01 03:00 UTC
As a software engineer, all of the free portion of the article is 100% correct about software engineering dysfunction.
There’s another reason why it is that way, though. A software engineer who is competent and productive and working under competent leadership making an useful product, would make a very large multiple of their salary in profits.
That permits all sorts of utter dysfunction while still breaking even on the average. You can have incompetent leadership in 90% of projects, you can saddle your developers with any kind of bad practices, you can impose all sorts of productivity damaging nonsense and yet still break even.
The dysfunction can be presented as relentless innovation and pursuit of new, uncertain opportunities, as a shrewd strategy.
If you fall below break-even, the consequences will not be visible for many years, and on the technical level it is piss easy to recover (it’s easier to do nothing than to convert your OS’s start menu to React).
This also relates to using AI to write code. You already can have a human write your code and pay them $1 for $10 you would make from it - or $0 if you fucked up. You want it to become $0.5 with AI coding tools? Then you’re multiplying your probability of success by what’s left after the probability that you get some unmaintainable slop . It’s simply not worth it.
Replies (1)
-
@jaschop@awful.systems 2026-08-01 05:47
You’re argument seems like Suresh’s to me, in that making working software is just laughably easy for a competent engineer. This begs the question why noone is exploiting this market gap. But there’s a couple explanations… It can be a coordination problem, in that there are just barely any competent software organisations with enough engineers. The problem can also lie in how software is bought, since customers seem completely unable to determine the competence of vendors. Perceptions on what kind of software is a safe, respectable choice may even be anti-helpful in this regard.