Roadmap

The deploy is done. Open it on your phone and laptop, tick a task on one, and see it on the other.

Playbook → Daily routine. Add them to your calendar as repeating events.

Playbook → Stay up to date. One general, one for your path, one for AI.

Playbook → LinkedIn, steps 1–4.

Playbook → Portfolio. Ask about the rules now; you pick the stories in months 7–9. Run the impeccable skill and pick 1 of 3 looks.

Playbook → GitHub, steps 1–3.

Playbook → Choose your path.

Mark what you already know. Note what excites you and what scares you.

Playbook → Choose your path → 5 questions. Prep, chat, write notes.

Same 5 questions. Ask what they wish they knew before switching.

Real code, real tests, a pull request to yourself.

Problem, who has it, what success looks like, what you will NOT build.

Who needs it, the API shape, limits, privacy, and how you would measure success.

Playbook → LinkedIn, steps 5–6. Drafts are ready to copy.

Then lock it in Settings. Not sure? Pick the best guess; you can switch at the Month 3 review.

Playbook → LinkedIn → step 11 has a ready draft.

Short lessons. Do the exercises, not just the reading.

One note per learning day: what you learned and one example. Real notes, never fake commits.

Pick one weekly chore (notes, specs, tests). Let AI write the first draft. Write down what worked.

Playbook → GitHub, steps 4–5. Put mowhcen.dev in your profile website field.

Playbook → Portfolio. Buy the domain on your personal Vercel account. Leave out any page you have not finished.

Skim it all once. Mark 5 topics you can't explain yet, then learn those.

Time how long it takes to make the first successful call. What made it easy? Write it up.

Ask first. Watch for trade-offs, not tasks.

Scalability, caching, load balancers, databases.

Options you weighed, what you chose, and why. This becomes the Decision part of the case study.

Use the case study template in the Playbook. Add a GIF and a link to it at the top of the README.

Open it on your phone, run Lighthouse, and paste the link in LinkedIn to see the preview.

What slows them down? What do they work around? This is discovery for technical users.

Non-functional needs are where Technical PMs earn trust.

If you switch, change it in Settings. Shared tasks you finished still count.

Ask your lead for a slot. Slides are optional; one clear story is not.

A real technical product. Playbook → Project ideas.

Quality, cost per use, speed, and what happens when the model is wrong.

Ask your manager first. Pick something small enough to ship in a month.

Same template as the Pace case study. Refresh the site while you are there.

Playbook → GitHub, steps 5 and 7.

Playbook → LinkedIn, steps 3 and 8.

Case studies first, only with your manager's OK. Then STAR: Situation, Task, Action, Result, one page each.