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
  • 3 Comments
Joined 9 days ago
cake
Cake day: November 5th, 2026

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


  • I get the appeal of a self-hosted tool, but my suggestion is to do the important ones in person.

    When I ran a Linux group years ago, the decisions that mattered were settled around a table. For a big decision, the dialogue and the discussion that lead to a common agreement are the real work, and in my experience no software does that part for you.

    For small stuff, a simple poll (or no poll at all) is fine: the core team decides and shares it as information. Save people’s attention for the decisions that need it.