How to use this

There is a course, and there is a set of tools around it. That can look like a lot at once, so here is the whole thing in two minutes: what to do in order, and what everything else is for. Read this once and you never have to wonder again.

The path, in order

This is the spine. Do it top to bottom. Everything else is optional support that hangs off it.

1. Do Setup first. Install everything the course needs, once, so you are never stopped mid-lesson hunting for a download.
2. Work the seven codelabs in order, one per week. Week four does not go well if week one never ran. Each week is built from short steps, none longer than a coffee.
3. Tick the checkpoint at the end of each step. That saves your place in this browser, so you can stop anywhere and pick up later. A codelab reopens where you left it.
4. Finish each week with its artifact. A repo, a Postman collection, a test suite. The thing you made is the thing you keep.
5. Paste each artifact into your Portfolio. Watching that list fill up, week by week, is the real progress bar, and the one you send with an application.
6. In week seven, apply. The portfolio is the point. Waiting to feel ready is a losing strategy.

The tools around it, and when to reach for each

You do not read these front to back. You dip into them at the moment you need them.

• Progress. Your dashboard: how far you are, per week and overall, plus your streak. Check it when you want to see the shape of things.
• Practice. Warm-ups for the core skill, understanding a product by testing it. Good before week two, or in any spare twenty minutes, using apps you already have.
• Glossary. Any term that is unfamiliar, in plain words. Search it and move on.
• Terminal 101. The page to read the moment a command fails and you are already annoyed.
• Git 101. What Git is, how it differs from GitHub, the everyday commands, and where else code can live.
• Mobile QA. Awareness of how mobile testing differs, mainly for interviews. Read it any time after week two.
• AI help. How to use an AI assistant to learn faster without fooling yourself, plus how to write a decent prompt.
• Resources. The master list of official docs and practice targets, when you want to go deeper on anything.

A realistic rhythm

This is built for a life with other things in it. You do not need long stretches.

• A few sessions of twenty to forty minutes a week is plenty.
• One or two steps per session is real progress. The checkpoint holds your place.
• Nothing important depends on a single marathon sitting.
• When a week feels tight, ship a smaller artifact rather than nothing. Done beats perfect.

Ready? Start with Setup, then open week one.