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

  • 1 Post
  • 7 Comments
Joined 11 days ago
cake
Cake day: November 5th, 2026

help-circle
  • I wish I’d had an AI assistant when I was teaching myself to code at 14, in a small village with no developers anywhere near me. My first stack overflow came from a recursive call, before I even knew what recursion was. It took me months to figure out. A patient teacher next to me would have found it in minutes.

    That’s how I’d use AI to learn: not “solve this for me” but “where’s the problem? Why? Teach me.” Used like that, it’s the knowledgeable, patient mentor most of us never had. Used the other way, it does your learning for you, and you learn nothing.





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


  • Totally agree with the conflict-avoidance answer. A small reframing: making mistakes is perfectly normal. A lie is usually an attempt to skip owning one.

    What makes you a mature person is:

    • Acknowledge it to yourself: nobody is perfect.
    • Plan the recovery: there’s a fix for everything but death. An honest apology is often most of it.
    • Own the fix: you dropped the bricks, so you pick them up. Don’t wait for someone else to do it.
    • Learn from it: making a mistake is fine, repeating it isn’t.

    A lie turns one mistake into two, and the second one is harder to undo.


  • Excellent advice, you don’t need anything complex, just install git and you’re good to go.

    Think of a commit as a save point before the boss fight. One rule is enough to start: commit every time something works, and always before trying something risky. Write the message as if for yourself in six months.

    The server can wait until you have something worth losing. Just remember git on one disk isn’t a backup: copy the folder somewhere else now and then.