constructive criticism: I'm a git user, but, if you need D3 graphics to explain a svc... can we at least accept that git concepts are not intuitive?
Visualizing Git Concepts with D3.js
41–50 of 52 posts
Re: Visualizing Git Concepts with D3.js
#42constructive criticism: I'm a git user, but, if you need D3 graphics to explain a svc... can we at least accept that git concepts are not intuitive?
We switched over to git from svn recently at work and the amount of confusion and accidents is crazy. I've been using git (mostly solo to two coworkers) for years, but there are still issues I run into where I'm stumped. I look things up all the time.
You kind of need git training in cases like this. Unfortunately, we didn't have any.
Re: Visualizing Git Concepts with D3.js
#43New to git as well as programming in general. This site has helped me somewhat, but I'm still confused about some basic concepts. Aren't the arrows all facing the wrong way? What happens to a commit after 'git reset' abandons it; can the commit be accessed ever again? What's the difference between reset and revert? How can merge and rebase be trusted? What are the best practices for how many branches a project should…
I 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…
for me, that git for computer scientists link was very clear
Re: Visualizing Git Concepts with D3.js
#44constructive criticism: I'm a git user, but, if you need D3 graphics to explain a svc... can we at least accept that git concepts are not intuitive?
May I ask what it is about git concepts that you find un-intuitive? To me personally, git makes a lot of sense conceptually, although the use cases of some commands can be a little confusing at first (e.g. `git checkout` for both switching branches and undoing changes to a dirty working copy).
Re: Visualizing Git Concepts with D3.js
#45See also "Learn Git Branching": http://pcottle.github.io/learnGitBranching/?demo
The Ungit[1] gui can also help you to visualize git operations like merging and rebasing commits. Here's the youtube demo: https://www.youtube.com/watch?v=hkBVAi3oKvo.
Re: Visualizing Git Concepts with D3.js
#46New to git as well as programming in general. This site has helped me somewhat, but I'm still confused about some basic concepts. Aren't the arrows all facing the wrong way? What happens to a commit after 'git reset' abandons it; can the commit be accessed ever again? What's the difference between reset and revert? How can merge and rebase be trusted? What are the best practices for how many branches a project should…
Not going to bother answering since I think everyone else has already covered it, but just wanted to say those are all the right questions.
Re: Visualizing Git Concepts with D3.js
#47constructive criticism: I'm a git user, but, if you need D3 graphics to explain a svc... can we at least accept that git concepts are not intuitive?
Oh, absolutely. I have yet to meet someone who didn't take several months to feel comfortable with it.
Re: Visualizing Git Concepts with D3.js
#48See also "Learn Git Branching": http://pcottle.github.io/learnGitBranching/?demo
The Ungit[1] gui can also help you to visualize git operations like merging and rebasing commits. Here's the youtube demo: https://www.youtube.com/watch?v=hkBVAi3oKvo . [1]: https://github.com/FredrikNoren/ungit
That's exactly what I was just thinking I wished existed!
Re: Visualizing Git Concepts with D3.js
#49I thought the new comments rule would ban the whiners, nitpickers and nay-sayers, but it seems all just like it was before. :O
Kudos to the developer, who made this tool.
Re: Visualizing Git Concepts with D3.js
#50This is probably my favorite post ever on HN.
Very enlightening. And, like lots of good things.... it's simple.
As others have mentioned, it would be nice to scroll down the diagram.
But, I guess if this were really wanted, git clone would be the first step:)