Remix.run Logo
▲ vouwfietsman 38 minutes ago

I think the exact opposite has happened: needless gatekeeping and NIH-syndrome has created this idea that software development is a skill that measures intelligence.

Because of this, battle-scars from the rough edges of software are seen as part of software-competence, not as a failure of industry. Novices get met with 'you're holding it wrong', but at the same time veterans lose the plot and spend most their time doing technical onanism, or worse, fighting meaningless complexity.

Until the stack exceeds any individuals understanding, and the cracks start to show. Leaky abstraction upon leaky abstraction upon layers and layers of ducttape, under the guise of HA, distributed system mantras, robustness, you name it.

Every part needing babysitting because every part is half the solution to half of your problem, but admitting that is seen as a skill issue.

Yes my DB dies because it caches stuff and (under obscure circumstances) never frees it: 'thats just MySql, deal with it', yes of course my frontend framework needs to be kept up to date every week because everyone is evalling strings all the time, 'don't you sanitize your input?', multiplied by every layer of the stack.

Don't you let your static analysis automatically merge security PRs so you can stay on top of this giant heap of string evals? No? That's best practice man!