Ctrl Zee
Engineer, 20+ years of project management, now tangled up in change management and AI. I share the mistakes behind the lessons: what I did, what broke, and the exact Ctrl+Z moment.
Blog: https://www.theundostack.org/ · Mastodon: @[email protected]
- 1 Post
- 3 Comments
Ctrl Zee@lemmy.worldto
Linux@programming.dev•Longtime Linux Developer Steps Down From Some Roles Due To Patch Flood Caused By AI
121·5 days agoSame here. Vibecoding my own tools is fine, because I’m the one who pays for the bugs. A kernel patch is different: thousands of people pay for them, so understanding every line is the minimum.
Anyone who sends code to public software should follow a simple code of ethics. A low barrier to entry is great, it’s how most of us started. But the bar for responsibility should rise with how many people run your code, and right now it doesn’t.
Ctrl Zee@lemmy.worldto
Linux@programming.dev•Longtime Linux Developer Steps Down From Some Roles Due To Patch Flood Caused By AI
761·5 days agoIt’s an unfortunate news, burnout in open source was real even before AI. Now it has just exploded.
Reviewing code has always been a bottleneck. AI made sending a patch nearly free, but reviewing one costs the same as ever, and it lands on a few volunteers.
For code that millions run, someone has to understand every line, so the sender should do that work, not the maintainer. Otherwise you’re just moving the cost onto the people who can least afford it.
There should be a simple rule: if you can’t explain your patch line by line, don’t send it. And maintainers should feel free to reject any patch by default when the sender can’t explain it.

Thanks for sharing such a personal story, Repair Cafés are a great idea, especially nowadays when “old tech” is still perfectly usable.
Curious: what were the biggest challenges you faced when setting one up?