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: @ctrlzee@mastodon.social
- 0 Posts
- 1 Comment
Joined 6 days ago
Cake day: November 5th, 2026
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
It’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.