Tootfinder

Menlo 看得有點疲乏了，換個字體：https://www.codingfont.com

Yesterday I got for myself the #book "The Ecology of Freedom" (a Spanish translation, I quite liked this particular edition ).
#books

"If anything, this author firmly believes that programming skills are second to those related to communication; most engineers coming out of colleges these days are unable to express themselves in public, to teach their peers, to write an essay or a blog post, to communicate their ideas to stakeholders, or to put together a simple documentation bundle without suffering a seizure in the process."
https://deprogrammaticaipsum.com/banning-adopting-reckoning/

🍿 #Tesla #boycottTesla #boycottMusk

Today @… was kind enough to share his encounter with an example of clean HTML versus ungainly HTML—for the same action on the same website.
🧵 1 of 5
#Accessibility #HTML

"It is no secret that the latest SARS outbreak has reshaped the world of work. Particularly in software engineering: where the work can be done anywhere with an internet connection so codes can be pasted from Stack Overflow, and the practitioners generally have a dislike of meetings. Your average software engineer would rather build the wrong thing for eight hours in a flow state, than have a 15-minute conversation in which they find out what direction they should go."
https://deprogrammaticaipsum.com/your-place-or-mine/

Happy , today I deployed a #Forgejo instance to manage my private code projects. I won't be using #Github anymore for my stuff, only to contribute to 3rd party projects.
I still have some pending work to configure the CI workers, but I'll leave that for next week.
Along the way I've learnt some stuff about #OpenTofu and networking. Enough to know that I still prefer to be on the dev side of the "devops" .

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.

"It is an interesting phrase, “the business”, especially when used by engineers to label the group of non-engineers in the organisation. It implies that everybody else is engaged in getting customers and making money, while engineering is a cost centre funded presumably through altruistic motives."
https://deprogrammaticaipsum.com/enough-agile/

"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."