I can't tell you how many times I nearly lost a week's worth of work early in my career because I was playing "version control roulette" with files named script_v1_final_FINAL_v2.py. It was a nightmare! I finally snapped and forced myself to actually learn Git properly, and it's the single best thing I ever did for my engineering efficiency. If you're still saving copies of folders to "back them up," stop it right now.

GitHub is basically the industry standard for a reason. It's not just a place to dump code; it's where the actual collaboration happens. For anyone starting from scratch, here is the mental model you need to survive and thrive.

The Git Mental Model

Git tracks every single change you make. Instead of multiple files, you have one file and a timeline of snapshots. You move your work through three stages:
1. Working Directory: Where you're actually typing code.
2. Staging Area: Where you pick which changes are actually ready to be saved.
3. Local Repository: Where Git stores the permanent snapshot (the commit).

When people tell you to "push your code," they just mean sending those local snapshots up to the GitHub servers.

Essential Setup & Security

Your GitHub profile is essentially your dev resume. Before you start pushing code, do two things:

Enable 2FA: Go to Settings → Password and authentication. Do not skip this. I've seen accounts get hijacked because of simple password reuse, and it's a pain to recover.

Create a Profile README: Make a public repo with the exact same name as your username. Whatever you put in that README becomes your landing page. It's the best way to show off your stack and projects.

The Only Commands You Actually Need

You don't need to memorize the entire Git manual. In my experience, 90% of a developer's day is spent using these few commands. If you master these, you're set.

# Initial Setup
git config --global user.name "Your Name"
git init                                # Start a repo in the current folder
git clone <url>                        # Copy a remote repo to your machine
Daily Workflow

git status                             # Check what's changed
git add .                              # Stage everything for a commit
git commit -m "Fix the login bug"      # Save the snapshot locally
git push                               # Upload to GitHub
git pull                               # Download latest changes from others
Branching (The "Safe Space" for features)

git switch -c <branch-name>            # Create and jump to a new branch
git merge <branch-name>                # Fold changes back into the main line

Getting this workflow down is the first step toward a professional AI workflow or any serious software deployment. Once this becomes muscle memory, you stop worrying about breaking things and start focusing on the actual architecture.