Tootfinder

techno-political rant
Say what you want about using the right tool for each problem, but there are tools that suck no matter what.
I'm tired of people portraying legit technical criticism as "biased" and "religious", while at the same time they present themselves as tolerant and open-minded (spoiler: for the most part, they aren't).
Almost every day of my life I have to deal with the nasty consequences of ultra-dumb decisions made by the very same people who are obsessed with productivity and criticise all day long whoever pushes for any design that shows any minim amount of care and/or deep thought (mostly via strawmen arguments).
And, of course, unironically: this has a lot to do with capitalism, as many of our other social and economic problems.
They arrive, have a strike of super-productivity for a few weeks/months and then use that as a trampoline to raise through the ranks or abandon ship before having to face the consequences of their technical crimes.
Then others arrive and are obviously slower at that same job... so the uneducated observers start believing that these newcomers aren't as good as the class traitors who wrote the initial nasty code.
To make things worse, if any of these newcomers dare to speak openly about introducing good practices... this ends up creating a new mental association (in the minds of uneducated observers) between "good engineering" and "lack of productivity".
The ones trying to fix the mess are indeed slower, not because they try to do things the right way though, but because they have to waste vasts amounts of time fixing what is objectively broken besides doing the "visible" work.
Most of today's established "super-productive" ones, if they were starting today, would be probably "vibe coders", certainly not what we commonly understand as a programmer. Not because AI-coding is the future, but because they never cared about the trade at all. They were here only for the grift.

"In this particular case, it is not uncommon for software developers to not only ignore, but even dismiss the required understanding of design language and primitives. At the same time, designers often lack the knowledge required to understand the various constraints imposed by software and hardware platforms."
https://deprogrammaticaipsum.com/the-impossible-dialogue-revisited/

"Go is a triumph in developer experience and efficiency, a language and a runtime created by very experienced designers built to solve a particular problem in a lightweight manner. Just like PostgreSQL and Git, some technologies survive Darwinian evolutionary cataclysms and rise to the top of their craft. Without any doubt, Go belongs to this select group, and if somewhat naïvely we take the past 15 years as a proof, its future looks definitely bright."
https://deprogrammaticaipsum.com/the-age-of-concurrency/

🎙️ Bienvenue sur 1Radio -Talk - Radio Libre
Musique inspirante, discussions authentiques et podcasts animés par des humains passionnés. 🎧✨
Rejoignez-nous pour découvrir des récits captivants et des sons uniques sur
https://1radio.ch. 🎶👥

"Maybe Dr. Weinberg took some inspiration from Melvin Conway, who in 1967 stated that “organizations design systems mirroring their own communication structures”. Now you start to understand why your microservice architecture is a mess, and no, neither Istio nor Prometheus is going to help you with that."
https://deprogrammaticaipsum.com/gerald-weinberg/

"My view of professional software engineering is one where I get to find out about people’s work and the problems they have, and try to solve them, and discussions are key to this project. If what I wanted to do were to have some uninterrupted time to discover how to shovel a Haskell into a BEAM on Kubernetes so I could scalable actor lambda, then yes, I could understand why understanding what the deliverables are would get in the way."