A practical guide series on Git - the version control system behind almost every modern codebase. How commits, branches, and merges actually work, how to fix the mistakes everyone makes, and the workflows real teams use on GitHub and GitLab. Written by people who use it every day.
Git in one picture: a change moves from your working directory, into staging, into a commit in your local history, then up to a remote everyone else can pull from.
Never used version control, or only ever typed the same four commands without knowing why? These three guides get you oriented.
The plain-English version: what version control actually solves, why Git won over the alternatives, and what a "commit" really is.
→The handful of commands that cover 90% of daily Git use, and the mental model - working directory, staging area, repo - that makes them click.
→Why branches are cheap and disposable in Git, how a merge actually combines history, and when you'll reach for each.
The moment Git gets genuinely useful - and occasionally frustrating - is the moment other people are pushing to the same repo.
What a remote actually is, the fetch/pull distinction people get wrong for years, and how Git relates to the platforms built on top of it.
→Why conflicts happen, how to actually read the markers Git leaves in your files, and a calm process for resolving them instead of panicking.
→The three ways to undo something in Git, what each one actually does to your history, and which one is safe on a shared branch.
APA Mastery runs live, practical sessions on working with modern AI tools - not just theory.
See What's On →The commands and workflows that separate "I can use Git" from "I'm comfortable with Git."
What rebase actually does to commit history, why teams fight about it, and a practical rule for when to reach for each.
→Trunk-based development, Git Flow, and feature branches compared - and how to tell which one actually fits your team's size and release cadence.
→Four commands that feel like cheating once you know them - shelving work, picking a single commit, finding the exact bug-introducing change, and recovering from "I think I just lost my work."
The core workflow, the undo-command decision table, and a rebase-vs-merge cheat sheet, as one printable PDF. Drop your email and it's yours, plus a heads-up whenever new guides go live.
No spam, unsubscribe any time.