@blabaere Possibly. Haven't looked into it enough to be sure but that feels plausible, at least for the old "write once, run everywhere" era of Java hype
@firebreathingduck There are many great observations in the post by @baldur, and in this video from @codesections (about the goals of programming groups at big tech vs developers creating "free software").
I see similarities in the tool stacks used in the #DataScience / #DataEngineering realm. It feels like there is a push to use no/low code, cookie-cutter, closed sourse, costly, inefficient, obfuscating tools that make it difficult to verify you're getting the "correct" answer, and a purposeful move away from craft and excellence. Commoditize, commercialize, and cross-#enshittify is the credo.
@baldur really insightful piece! It’s been pretty obvious that recent layoffs and some of the AI hype has been about labor discipline but I hadn’t thought of how frameworks and technology choices also serve this purpose.
Perhaps also related is how tools like LinkedIn, Indeed, Glassdoor push a certain individualist framing of job market that claims to be about empowering workers but curiously bereft of any labor organizing. Know of any research or analysis on this topic?
@baldur Oh Baldur, this is just so, so sharp. Gonna be thinking about this the rest of the day. Thank you.
(And I hope you know how downright humbled I feel, after seeing you closed with such an expansive endorsement of my little book. Thank you so much, Baldur — that really means a lot 💜)
@baldur Some lines hit really close to home. After years of "we need to hire more people to do this right" and equally many years of "we can't afford that, CTO won't give us the budget", reading something like "They will let their own businesses suffer by shipping substandard software because they believe they can recoup those losses at your expense." is really painful to bear.
@baldur One thing I'm not certain about is what makes one piece of technology "okay", say, a C++ compiler, but others problematic, like a web component framework? Both do essentially the same, encapsulate knowledge and hide the dirty details from the developer.
It's easier to hire C++ programmers than assembler programmers - yet I don't think many developers would say we should go back to hand written assembly.