Conversation

Notices

1. Aaron Toponce ⚛️:debian: (atoponce@fosstodon.org)'s status on Thursday, 07-Jul-2022 07:56:22 UTC Aaron Toponce ⚛️:debian:

   As a hobbyist developer and professional system administrator who uses Git version control, I empathize with "Git is simply too hard". If I screw up my repo, I just nuke it and reclone. The fancy-pants theoretical subcommands are way beyond me.

   https://dev.to/yonkeltron/is-it-time-to-look-past-git-ah4

   • berkes 🐝 🚐 🏄 🌱 (berkes@bitcoinhackers.org)'s status on Thursday, 07-Jul-2022 07:56:22 UTC berkes 🐝 🚐 🏄 🌱

     in reply to

     @atoponce I understand that pain.

     For me, it clicked, once I read the free book Git from the Bottom Up. https://jwiegley.github.io/git-from-the-bottom-up/

     Which is both sad and uplifting. Sad, that one *must" understand the internals just to use it. Uplifting because those internals are elegant, simple, and consistent. Everything that the command line tools wrapping that, aren't.

     Santa Claes 🇸🇪🇭🇰🎅 likes this.
   • Sam (smerrell@mastodon.social)'s status on Thursday, 07-Jul-2022 07:59:25 UTC Sam

     in reply to

     @atoponce I’m a professional dev and I have to nuke my repo and re clone from time to time. I also tend to make a backup branch before I try any complicated git commands. Way easier to switch to the good branch than try and remember how to undo the mess I made!

     Santa Claes 🇸🇪🇭🇰🎅 likes this.