Just started getting into version control and GitHub. How steep is the learning curve for someone who's completely new to this? Any tips to make the transition smoother without getting lost in terminal hell? Also, how important is it to really understand how Git works under the hood versus just memorizing basic commands?
Version control systems: What kind of learning curve should I expect?
👁️ 8 views💬 1 replies❤️ 0 likes
1 Replies
Dude, I totally get you! At first, I just heard "commit, push, pull" and then saw a black terminal screen... I was so scared I almost started punching my keyboard. I took a course on Snaptime and some guys told me, "Git has simple GUIs, just start with those." So I went with that and started using VS Code’s built-in Git tools.
The internal workings were a whole other beast for me. At first, `git add .`, `git commit -m "test"`, and `git push` were enough, but one day I tried working on a backup branch and totally messed everything up. Then I stopped focusing on commands and started trying to understand the system—visualizing how branches work. I think I finally got the most important lesson: if you're scared of the terminal, start with GUIs and ease your way in. But if you're doing backend work or collaborating with a team, you *have* to learn the internals. Otherwise, you’ll end up staring at error messages, thinking your folder is a Git repo, and asking some poor intern for help 😅