You know, while I was in coding bootcamp, I welcomed the opportunity to get into Git during my capstone group project. I became familiar with git pull, git push, git add, git commit and git clone; I coded and Git-ed away like a well-oiled Tonka Truck 🚒
Well, enter my first dev job. Now it's git checkout -b (or is it git checkout without the "b"?), git fetch, git merge, git reset, git rm, git log, git diff ... and what is this upstream?? Upstream relative to where?? And I ain't even touching git rebase until I'm super-clear on what it does 😆
My point is: I wonder if I could have learned as much Git as I have these last 2 weeks in a personal-project or bootcamp setting. Honestly, I highly doubt it. The pressure of working on production code is pulling skills and abilities out of me that I didn't know I had. So for those of us still on the hunt for our first dev job, I think that the closest we can come to a similarly-pressured environment is to join a robust, well-maintained and ACTIVE open-source project (like Dev.To!).
Before I started working, I attempted to join several opensource Rails projects, and Dev.To was the ONLY one that was a breeze to configure and fire up on my local environment. What's more, their GitHub community is very responsive and supportive. Grab one of their [good-first-issue] issues, or be bold and ask to pair with someone working on a more complex issue. Get in there, my fellow devs, and build some real Git muscles! You'll thank me! 😉 🧡
Top comments (5)
Be sure to check
git reflogas well. It will come handy eventually.Git checkout -b when you want to make a new local branch,without -b when you're switching between branches. Hope this helps. 🙂
or you can just use sourcetree. It's better
Wow, great to hear that we had an easy set up!
This is a great suggestion for anyone wanting to get into git more (like me). Thank you!
Some comments have been hidden by the post's author - find out more