Chapter 1 · Lesson 3

How to Get the Most from This Course

Adopt a simple read-then-do learning strategy that makes Git stick long after you finish reading.

11 min read Text Updated 2 hours ago Free preview

In this lesson you'll learn

Adopt a simple learning strategy that makes Git stick.
Keep the skills with you long after you finish reading.

You can read about Git all day and still feel lost. The trick is that Git is a skill, like riding a bike — you learn it by doing, not just by reading. This short lesson gives you a method that works, so the time you spend here actually pays off.

The core strategy: read, then do — immediately

Here is the whole method in one sentence: read a small idea, then run it yourself right away, and repeat.

Do not save all the typing for "later." Later rarely comes, and the idea fades fast. When a lesson shows a command, switch to your terminal and run it before moving on. The gap between learning and doing should be seconds, not days. This is how a fact in your head becomes a skill in your hands.

The learn-by-doing loop: read an idea, try it, sometimes break it, fix it, and come away truly understanding — then repeat.

Type the commands yourself

It is tempting to copy and paste every command. Please don't — at least not all the time. When you type a command yourself, your brain notices each piece: the program, the options, the file names. That tiny bit of effort is what turns "I saw it" into "I can do it."

💡 Tip

Keep a terminal window open right beside this course as you read. Treat the two like a recipe and a kitchen: you read a step, then you do it, then you read the next.

⚠️ Watch out

Copy-pasting blindly is the number-one reason beginners feel stuck. When something goes wrong, they have no idea which part to fix because they never really read it. Slow down and type — it is faster in the long run.

It is okay to break things

You will make mistakes, and that is part of the plan. Remember the "without fear" promise from Lesson 1.1: in Git, almost everything can be undone. So when an exercise says "try this," go ahead and experiment beyond it too. Breaking something and then fixing it teaches you more than ten lessons where nothing ever goes wrong.

Use the downloadable resources

This course comes with handy reference material you can keep beside you:

A command cheat-sheet — every command you learn, on one page.
A glossary — short, plain definitions of every Git term.
Checklists — for example, the steps to publish your project at the end.

You do not need to memorise commands. Real developers look things up all the time. The cheat-sheet is there so you can focus on understanding rather than remembering.

Follow the 🧵 course project

Instead of random throwaway exercises, this course threads one real project through every section: a small personal website called "My Dev Portfolio." Whenever you see the 🧵 marker on a lesson, you are adding another piece to that same project.

This means your practice compounds. By the final section you will not just "know Git" — you will have a complete, published portfolio you built with your own hands. You will meet this project properly in the next lesson.

A simple weekly rhythm

If you only have short bursts of time, aim for one section at a sitting. Read it, do every hands-on step, take the checkpoint quiz, then stop. Small and consistent beats long and rare.

Lesson Summary

You learn Git by running Git — keep a terminal open beside the book, type commands yourself, and let the 🧵 project turn practice into something real you can show off.