Top all-time · #1709
Tv's cobweb
Personal blog · eagain.netprogrammingsystems
Tv's cobweb is a personal blog at eagain.net about programming and systems. Since 2007, 45 different Hacker News readers have linked it 52 times, most often “Git for Computer Scientists”. The last post was in 2016, but the archive is still widely read.
Most-linked posts?
- Git for Computer Scientists23 people · 25 mentions · first linked 2007-07-17
- Git for Computer Scientists (2010)14 people · 15 mentions · first linked 2020-07-11
What Hacker News says?
Take a look at https://eagain.net/articles/git-for-computer-scientists/ ? Maybe you've already read it, but this is what let me grok the underlying data.
Comment linking /articles/git-for-computer-scientists/
on “Git undo: We can do better”Submitted Git for Computer Scientists (2010) as a story · 259 points
HN discussionSee also http://eagain.net/articles/git-for-computer-scientists/
Comment linking /articles/git-for-computer-scientists/
on “Git from the inside out”Submitted Git for Computer Scientists as a story · 103 points
HN discussionWith all these recipies - one thing I do whenever I attempt some stunt in git: I assign temporary tags to every changeset that's important. git tag tmp git perform-stunt This eases undoing the stunt without needing to find the "before" state from reflog. And if you use a graphical log viewer (I like SourceTree on Mac) you'll see the tagged state in the history view - which makes things a lot clearer. And to be aware…
Comment linking /articles/git-for-computer-scientists/
on “Some bad Git situations and how I got myself out of them”Submitted Git for Computer Scientists as a story · 70 points
HN discussionI gained a better understanding of git through this document: https://eagain.net/articles/git-for-computer-scientists/ I'm not a computer scientist and I think it's understandable. Everything became a lot more clear in my mind once I understood the inner workings.
Comment linking /articles/git-for-computer-scientists/
on “Magit, the magical Git interface (2017)”Submitted Keyboards Influenced by Touchscreens (2011) as a story · 16 points
HN discussionI found git to make a lot more sense personally after reading http://eagain.net/articles/git-for-computer-scientists/ . The git parable is also very good.
Comment linking /articles/git-for-computer-scientists/
on “Git Is Simpler Than You Think”Submitted Dynamic JSON in Go as a story · 8 points
HN discussionI found this very helpful: http://eagain.net/articles/git-for-computer-scientists/ . Git's data structures are well designed. Once you have internalized them, you will be better equipped to navigate through the jungle of command-line options. To understand the data structures interactively, use "git cat-file -p HEAD" and continue drilling down to an individual file in a subdirectory with "git cat-file -p OBJECTHASH "
Comment linking /articles/git-for-computer-scientists/
on “How to teach Git”Submitted Quick introduction to git internals for people who are not scared by words like Directed Acyc. Graph as a story · 4 points
HN discussionHave you seen this one? https://eagain.net/articles/git-for-computer-scientists/
Comment linking /articles/git-for-computer-scientists/
on “Ask HN: What's the worst piece of software you use everyday?”Submitted Git for Computer Scientists as a story · 3 points
HN discussionThe CLI is indeed hard to learn. But the simplicity of git is not using it, it's its internal structures: http://eagain.net/articles/git-for-computer-scientists/ If you understand these, then three stages to "commit to server" won't seem too many to you. (Often you don't need the index-building stage ("add"), and then you can say "git commit -a"). What people complain about is often the CLI's inconsistency. For exam…
Comment linking /articles/git-for-computer-scientists/
on “Gitless: a version control system”Submitted Git for Computer Scientists as a story · 3 points
HN discussionI thought all we needed was the short "Git for Computer Scientists" [0], which consists mostly of images and which had me saying "oh, that wasn't so hard after all". [0] http://eagain.net/articles/git-for-computer-scientists/
Comment linking /articles/git-for-computer-scientists/
on “Key Git Concepts Explained the Hard Way”Submitted Git for Computer Scientists (2010) as a story · 2 points
HN discussionGit isn't designed for "noobs trying to pick up coding just to experiment". It also isn't really designed for solo developers as the OP is about. Git is designed for collaboration. Git's UI is absolutely unintuitive, especially coming from other version control software. But that's irrelevant. Everyone wants to use it because of the network effect. In terms of _why_ the UI is unintuitive, I believe it's because it i…
Comment linking /articles/git-for-computer-scientists/
on “Git In Two Minutes (updated after 8 years)”Submitted Git for Computer Scientists as a story · 2 points
HN discussionI can attempt to answer your questions briefly Aren't the arrows all facing the wrong way? >> No, the arrows are in the right direction. Git maintains a Directed Acyclic Graph (DAG) of commits. Each new commit created points to 0..n parents. So let's say you were on the first commit, and then you created a new commit. The newly created commit is the "child" of the first commit, and has a "parent" pointer that is the…
Comment linking /articles/git-for-computer-scientists/
on “Visualizing Git Concepts with D3.js”Submitted Git for Computer Scientists as a story · 2 points
HN discussionGit for computer scientists: http://eagain.net/articles/git-for-computer-scientists/ Quick introduction to git internals for people who are not scared by words like Directed Acyclic Graph.
Comment linking /articles/git-for-computer-scientists/
on “Git koans”Submitted Git for Computer Scientists as a story · 2 points
HN discussionThis is surprisingly straight-forward: http://eagain.net/articles/git-for-computer-scientists/
Comment linking /articles/git-for-computer-scientists/
on “Git in six hundred words”Submitted Git for Computer Scientists as a story · 2 points
HN discussionSee also Git for Computer Scientists at http://eagain.net/articles/git-for-computer-scientists/
Comment linking /articles/git-for-computer-scientists/
on “Git concepts simplified”Submitted Git for Computer Scientists (2010) as a story · 1 points
HN discussionBetter pattern is http://eagain.net/articles/go-json-kind/ Then you do one switch to get the correct message type to decode into, and boom, you can just `.Run` or `.Handle` or however you design the interface, and you are done.
Comment linking /articles/go-json-kind/
on “Ditching Go for Node.js”Submitted Unmarshaling a heterogeneous JSON array into a Go struct as a story · 1 points
HN discussion
