www.eamoncaddigan.net

Content and configuration for https://www.eamoncaddigan.net
git clone https://git.eamoncaddigan.net/www.eamoncaddigan.net.git
Log | Files | Refs | Submodules | README

index.md (2384B)


      1 ---
      2 title: "Useful and interesting Git posts"
      3 date: 2024-02-11T20:00:20-08:00
      4 draft: false
      5 categories:
      6 - Programing
      7 tags:
      8 - Git
      9 ---
     10 
     11 This is just a collection of interesting (and not necessarily recent) Git
     12 posts from around the web. I may update this as I find new things.
     13 
     14 ## Introductions
     15 
     16 [Mikkel Paulson --- Git is my buddy: Effective Git as a solo
     17 developer](https://mikkel.ca/blog/git-is-my-buddy-effective-solo-developer/)
     18 
     19 I love reading about how other people use Git, and like Mikkel I am usually
     20 using it as a “solo developer”. It’s interesting how different his approach
     21 is from my own. I think that’s partly due to us being in different lines of
     22 work (I haven’t been paid to put anything on the web since the 1990s), but
     23 it also suggests that I could be doing things better.
     24 
     25 [Sandra Snan --- The life-changing magic of
     26 git](https://idiomdrottning.org/git)
     27 
     28 A nice introduction to Git. I really appreciate how it defines the most
     29 common pieces of Git jargon.
     30 
     31 [Nick Farina --- Git is simpler than you
     32 think](https://nfarina.com/post/9868516270/git-is-simpler)
     33 
     34 This is an older post, written at a time when many programmers were still
     35 using Subversion, and it’s worth checking out for the vintage screenshots
     36 alone. But it also serves as a great introduction to what Git is doing
     37 under the hood.
     38 
     39 [Julia Evans --- Inside .git](https://jvns.ca/blog/2024/01/26/inside-git/)
     40 
     41 This comic (with accompanying text) goes even deeper into what Git is
     42 actually doing. A “Git repository” is just regular directory full of source
     43 code (or whatever) called the “working copy”, plus a .git directory
     44 containing a collection of special files. This breaks down all those files.
     45 
     46 ## Opinions
     47 
     48 [Dan Kelch --- Nobody cares about your Git
     49 history](https://spin.atomicobject.com/git-history/)
     50 
     51 You can ignore the provocative title (or appreciate it), but really this is
     52 good guidance on how to think about rebasing vs. merging.
     53 
     54 [Alex Kladov --- Git
     55 things](https://matklad.github.io/2023/12/31/git-things.html)
     56 
     57 “A grab bag of less frequently talked about git adjacent points.” The stuff
     58 about CI and code review is always fascinating to me---a “solo
     59 developer”---a window into a whole other world of writing code for a living.
     60 The tips for working on merge commits are great, and I’ve adopted Alex’s
     61 advice on moving files and starting with empty commits.