5 ms·
Definitely helped a bit. I just graduated from university and am working full time as a developer now. I thought I knew how to use git because I knew how to do
by jjice 5y ago
Definitely helped a bit. I just graduated from university and am working full time as a developer now. I thought I knew how to use git because I knew how to do feature branching and merging. Boy was I wrong. Within a few weeks at my new job, I've realized that I'm missing so much useful git knowledge. When I learned about cherry-pick, my mind was blown.
My goal right now is to develop a better mental model of git than what I have right now. If anyone has recommendations for resources, please let me know!
- guhidalg 5y agohttps://learngitbranching.js.org/ https://learngitbranching.js.org/ Go through every lesson, understand it, and find yourself more knowledgeable about git usage than 95% of developers.
- lanstin 5y agoSo true and so worth the extra knowledge to understand your tools. You should also read about the various knobs on your compiler or interpreter from time to time. I used to reread gcc manual every five years, and now I search on the env variables that affect python runtime. Getting ready to that for go build chain now I have 3 or 4 production go things. Similar for my editor and libc and language stblib and kernel APIs, tho they are more diffuse than the gcc manual.
- Forge36 5y agoThis was a good way to pass some time :) I look forward to sharing this with others on my team.
- jlokier 5y agoThis was the best resource for me: http://ftp.newartisans.com/pub/git.from.bottom.up.pdf http://ftp.newartisans.com/pub/git.from.bottom.up.pdf
- leephillips 5y agoThat is a good, clear exposition. Thanks!
- macintux 5y agoJessica Kerr (jessitron) gives a good git internals talk that you can find on YouTube if that’s a helpful learning style.