New Raiders HC Klint Kubiak credits alignment with John Spytek as early priority https://raiderramble.com/2026/02/11/new-raiders-hc-klint-kubiak-credits-alignment-with-john-spytek-as-early-priority/
I've been talking before why money won't solve the burnout problem. But let's for a minute assume that you really wanted to help people maintaining #FreeSoftware by paying them. The problem is that:
1. You have to pay them a living wage.
While all monetary help is appreciated by developers, they need a living wage. Not "that should prevent you from starving to death" but the kind of money that can support a honest (but not lavish) lifestyle: pay the bills, feed your family, cover other living costs such as repairs, clothes, appliances, and let you save enough for future emergencies.
It's simple as that. If you can't do that, they're going to need a dayjob. If they're lucky, it won't collide with their #FLOSS work. If they're not, it will kill them. Or they'll fall somewhere in the middle, slowly burning out until they can neither maintain their projects, nor work.
2. You need to guarantee that the payouts will continue.
People need security. They're not going to stay unemployed, let alone quit their job or turn down a job offer, unless they either have good guaranties or substantial savings (or they're in a really bad shape and wouldn't be able to handle the job anyway). The job market is hell, and people just know that when the payments stop, they may not be able to find a job soon, let alone a good job. Even "passively" looking for a job can burn you out.
So yeah, one-off payments and pinky swears won't do. And it isn't even a matter of whether we can trust you; it's a matter if you'll actually be able to continue paying us. And honestly, I don't really know how to solve that. Perhaps by paying up front, but for how long? Finding a job may take more than a year, finding a good job may be once-in-a-lifetime opportunity.
3. It can't end up being a job.
Perhaps most difficult of all, these payments can't really come with explicit obligations. I mean, that's the whole point: you want to support FLOSS, not turn it into a corporate project. You want the maintainer to remain free and enjoy the work. That is unlikely to happen if their livelihood is now dependent on your satisfaction. And even if it isn't, I for example would still feel indebted to whoever's paying me to do FLOSS, even if they really didn't expect anything in return, and would fall into a spiral of guilt-inflicted burnout if I failed to maintain the software satisfactorily.
#OpenSource
Took the day off to head up to Natural Bridge State Park with my wife. Pictures don’t really do justice to how massive it is.
Then there are the Blue Ridge Mountains, always gorgeous. Will return to Skyline Trail later this summer, as it’s an official International Dark Sky viewing location. Perhaps in August for the Perseid meteor shower season.
🇺🇦 #NowPlaying on #BBC6Music's #NewMusicFix
Worsleyy:
🎵 Northern Step (feat. Chimpo)
#Worsleyy
https://worsleyy.bandcamp.com/track/northern-step
https://open.spotify.com/track/5uN8qtXFOl8j91njYZmW5w
Sen. Steve Daines announces he will not seek reelection (Politico)
https://www.politico.com/news/2026/03/04/steve-daines-montana-senate-retirement-2026-election-00813633
http://www.memeorandum.com/260305/p41#a260305p41
Yesterday, I've read a vibe coded script for the first time in my life, and I've cried.
It wasn't ugly. "Ugly" is not the right term. It was as if someone wasn't able to comprehend beauty, but badly tried to mimic it. It felt like "malicious compliance" to beauty. The kind of awful verbose pedantry that feels wrong every step of the way.
It's the kind of code you'd expect in a corporate environment when you know that the code would be read by the top suits who have no idea about coding, but judge it by the volume and expect science fiction level of make-believe.
It's the kind of code is abstracted away into the tiniest details. Every function returns a complex dataclass explaining precisely what it did, for no reason at all. What would be two lines of code is a function. What would be a function is a whole module. It's a caricature of good programming practices.
I was supposed to add modifying a second field on the same object via GitHub API. I've guessed it would take me about an hour to figure out the code enough to be able to do that — what ought to be 2-3 extra lines. I suspected I'd discover that most of the code does precisely nothing. Just meaningless API exchanges that are absolutely unnecessary. It felt like the kind of parody of bureaucracy where you have to file 10 forms to do something, and only one of them actually means anything.
What used to be "do one thing well" became "doing ten totally random things is fine, as long as one of them happens to be what I need, and the whole thing doesn't blow anything up in an obvious way".
Perhaps it's just because this way a throwaway script. Maybe "production" stuff takes more, err, prompt refining? Maybe it actually can produce stuff that's comprehensible.
But if that code was any indicator, then I'm not going to believe that any big LLM contributions are actually reviewed by humans. A review will take more time than rewriting from scratch. This is a ticking time bomb. That LLM-generated code isn't introducing exploits right now is either a statistical accident, or it's just that nobody bothers.
Clarification: I didn't "prompt" it or request one. I'm not a hypocrite.
#NoAI #NoLLM #AI #LLM
Kirk Cousins on 4th NFL stop with Raiders: ‘I’d like to still do this’ https://raiderswire.usatoday.com/story/sports/nfl/raiders/2026/04/08/kirk-cousins-on-4th-nfl-stop-with-raiders-id-like-to-stil…