#git posts — Ben Crowder https://bencrowder.net/blog/tag/git/ Feed for blog posts tagged with #git. Sat, 25 Apr 2026 20:02:35 GMT en-US https://bencrowder.net/ Links #7 https://bencrowder.net/blog/2020/links-7/ https://bencrowder.net/blog/2020/links-7/ Fri, 21 Aug 2020 12:00:00 GMT
  • Agnes Callard on why difficult old books make for independent minds — an interesting point I hadn’t thought much about before
  • C. S. Lewis on reading old books — I reread this in connection with Agnes’s post and it’s still good
  • Austin Kleon on books with unusual but brilliant structures — this kind of thing fascinates me
  • Oz Nova on the cost of forsaking C — while I hardly ever program in C anymore and it’s still a footgun, I actually like it a lot
  • Swyx on moving the default Git branch from master to main — something I’m planning to do with my personal repos

    • Reply via email

    ]]>         Just came across Flight rules for Git and it’s the kind of thing I’ve wanted for years. For example:... https://bencrowder.net/blog/2018/630/ https://bencrowder.net/blog/2018/630/ Wed, 17 Oct 2018 12:00:00 GMT Just came across Flight rules for Git and it’s the kind of thing I’ve wanted for years. For example:

    • “I wrote the wrong thing in a commit message”
    • “I accidentally committed and pushed a merge”
    • “I want to discard specific unstaged files”

    Great structure, very helpful. Highly recommended.

    Reply via email

    ]]>         A thought on writing novels https://bencrowder.net/blog/2015/a-thought-on-writing-novels/ https://bencrowder.net/blog/2015/a-thought-on-writing-novels/ Wed, 11 Nov 2015 12:00:00 GMT As I’m now starting to get more serious about writing novels, I recently made a list of the next few books I want to write after the one I’m working on, and I ran into an unexpected side effect: knowing what the next few items in the queue are has somehow made writing a novel feel far more doable. It’s now a task that has an ending, rather than being something with no end in sight.

    Sidenote: I’m not sure how much I’ll talk here about the novel in progress, at least not until I finish a full draft, but I do plan to talk about tools and process. (For example, I’ll write more about this later, but I’m using Vim with a Git repo and a post-commit hook that generates a print-ready proof PDF of the full book via TeX whenever I commit.)

    Reply via email

    ]]>