"Quite simply, if you have not read this book yet, read it. If you have a colleague who has yet to read it, get them a copy. If someone asks you what one book to read about software engineering, it is this one. It is not Code Complete, Second Edition, nor is it Clean Code, nor any other book that claims to teach you how to get software right the first time around (you will not)."
https://deprogrammaticaipsum.com/michael-feathers/
PSA: Do you have a carbon monoxide detector in your home? Do you have more than one (think redundancy)? Does it have a fresh battery (or lifetime battery)? Have you tested the alarm function recently?
If you have appliances that may create carbon monoxide, or an attached garage, now is a good time to check all of the above.
#CarbonMonoxide
#todayilearned that methane emissions from EU marine transport have at least doubled between 2018 and 2023, largely due to increased use of #LNG. [1] Methane is a heavy contributor to #climatechange
"Simultaneously to Steve Jobs’s introduction of the iPhone in January 2007, Google started publishing a series of blog posts called “Testing on the Toilet”. On May 15th, 2008, this series featured a famous issue: “TotT: Using Dependancy Injection to Avoid Singletons.” The writing was literally on the wall of toilets worldwide: Singletons are bad™®©. Sadly, the much more exciting idea of dependency injection contained in the article got lost in the minds of most readers."
https://deprogrammaticaipsum.com/the-hype-cycle-of-oop/
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
Super happy to see the open source sysdiagnose joining the hackathon.lu held in Luxembourg on April 8th and 9th, 2025.
sysdiagnose is an open-source framework developed to facilitate the analysis of the Apple sysdiagnose files and especially the one generated on mobile devices (iOS / iPadOS). In the light of targeted attacks against journalists, activist, representatives from the civil society and politicians, it empowered incident response team to review device behaviour and ensure th…
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.
uspolitics, trump
I keep seeing smart people writing stuff like
> [the US] kept peace through strength balanced with restraint, and wielded influence through culture, values, and diplomacy
I understand that #Trump is terrible and some people feel tempted to idealize what they had before him, but we should be more discerning, or otherwise it becomes impossible to understand how this happened in the first place.
Let's start with some questions:
- peace where? and for who? was it true peace, or "Pax Romana"?
- are we going to take seriously that statement on "restraint"? after all the lies, internal witch hunting, sanctions, coups, wars, invasions, genocides, and last but not least, 2 unnecessary nuclear strikes on Japan?
Now, on "culture, values, and diplomacy". Sure. Why not. Not everything was going to be bad, right?
But the thing is, abusive husbands aren't bad all the time either. From time to time they know how to be sweet and seem to care: one present here, flowers the next day, a little bit of gaslighting, and fake apologies after that "accidental" slap.
Given enough time (if the wife is still alive), at some point the victim decides to leave, and then all hell breaks loose. Trump is the manifestation of that moment. He does not represent a change in #USA's nature, but a hidden side that was "always" there, just waiting to play its role.
Others believe this is because #US citizens have been intentionally dumbed down by a combination of propaganda and a disfunctional education system, and I'm sure it's partly true... But let's see what many of their most brilliant and educated citizens are choosing to do with their lives today: https://sfstandard.com/2025/03/12/stanford-students-want-in-on-the-military-tech-gold-rush/
So, all I'm asking is: please drop the act. It was always a clusterfuck.
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" .