• 0 Posts
  • 20 Comments
Joined 2 years ago
cake
Cake day: August 8th, 2023

help-circle










  • Louis makes a lot of the points you’re making in the video. He points to Clippy as an example of universal repulsion where we “didn’t know how lucky we had it”, versus the wolf dressed up in social media’s clothing we have today.

    I agree with a lot of what you said, but it’s still worth watching the video. His overall aim is an honourable one and the choice of Clippy is pretty smart in light of the aims.








  • This is the reality. You’ll spend most of your time working with people of varying SCM skill levels, and spread all the way across the spectrum. Squash commits combined with centralised auditing (GHE, GitLab, etc) add the necessary rail to keep a clean history on main and to make building-block change sets easily revert-able.

    In my decades working on large teams of engineers, the need to identify changes by wip/interim commits has never been terribly useful for the reason you describe: everyone has different git hygiene procedures and most corps don’t give a tiny little shit about maintaining that level of hygiene unless you’re white room / highly regulated.

    And if you do want that level of depth you can go find the PR/MR in the central source where the revision history of the dead branch is often sustained (unless you configure it not to)

    But yeah, I call YAGNI a lot on git history purists to this day. It’s a huge amount of effort and coordination to retain a tiny amount of value that is 50/50 gonna be useful depending on the git hygiene of the person who wrote it. Save your efforts and just read the damn code.