| ▲ | TacticalCoder an hour ago | |
It's because amateurism has been hailed as the second coming of Christ. Leftpad, mentioned in TFA, is a case in point: not because of leftpad itself but because of all those defending leftpadism. "People can't write a proper leftpad". Yeah, well... If a dev cannot write a proper leftpad, then it should never have been a dev in the first place. Someone who cannot write leftpad is not qualified to use leftpad as a dependency (and, no, leftpad is neither the Linux kernel nor a cryptographic libray: it's fucking leftpad, which is the entire point). We've had "devs" whose only qualification was writing glorified "punch the monkey" ads in JavaScript: the JavaScript surveillance/ad complex. Devs who only ever knew the mono-threaded JavaScript ecosystem and suffered from heavy leftpadism. And those very same surveillance/ad complex bros are now generating countless crap with LLMs, in languages they don't understand. They're just mediocre. That's what happened: the veneration of mediocrity. | ||
| ▲ | Apocryphon 38 minutes ago | parent | next [-] | |
You're repeating points that were brought up in the discussions about leftpad a decade ago, but the root cause wasn't venerating amateurism (even though the everyone can code / software bootcamp trends of the time was a by-product of it); it was the veneration of velocity. Which, I suspect, is inevitable in software because it's so powerful, low-resource intensive, and lucrative compared to other engineering disciplines. This technology was always going to create an industry focused on speed above everything else. | ||
| ▲ | vouwfietsman 32 minutes ago | parent | prev [-] | |
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! | ||