Step 1: Set your daily routine

1. Pick a fixed time slot each day. Mornings work best for me (07:30 to 08:00, before the team is online). If mornings are impossible for you, pick another window you can actually defend. The exact hour matters less than picking one and not negotiating with yourself about it every day.

2. Block it in your calendar. Treat it like a client meeting. I label mine "Prep, do not book" and I've declined real meetings on top of it.

3. Decide the focus type for the day, not the exact topic. Learning, coding practice, or self-review. That's the call you make the night before. Picking the exact closure exercise at 07:29 in the morning is how the slot dies.

4. Show up even when the day is on fire. There will always be a production incident or a tight deadline. Skip once, and you'll skip again. The week I broke my 2019 streak started with one "I'll do it tomorrow" on a Monday.

Step 2: Create a personal roadmap calendar

Once the slot is sticking (give it two weeks before you trust it), spend a few of those slots designing the next 3-4 weeks. That gives you a shape, so you don't open your laptop at 07:30 and waste ten minutes wondering what to study.

How I do it:

1. Read through every lesson in this chapter once. Don't take notes yet, just get the map.

2. Get to the last lesson and draft the calendar there.

3. Write tasks that are specific, time-bound, and linked. Example:

   • "Tuesday → Read web.dev JavaScript - Closures"
   • "Wednesday → Record a 10-minute video answering 3 questions (self-prompt: Explain how React's rendering cycle works)"
   • "Friday → Solve a short UI coding challenge from Frontend Mentor"
   • "Monday → Watch React Docs - Thinking in React"

   Every task has the link sitting right there. When 07:30 hits, you click, you start. No deciding.

4. Plan in cycles, not months. Three to four weeks at a time. At the end of the cycle, look back at the calendar and ask one honest question: which sessions did you actually enjoy? My last cycle, I noticed I kept skipping the live coding slots on Thursdays and binging React docs on Sundays. So the next cycle moved coding to Sunday morning, when I had the energy for it, and the skip rate dropped to zero.

Step 3: Make it yours

Two shapes that both work:

• Focused: one subject per cycle. All HTML, then all JS, then all CSS.
• Mixed: one topic per day. Today theory, tomorrow recording, the next day a coding challenge.

I run mixed, and I've tried both. Focused cycles burned me out by week two (four straight days of CSS specificity reading and I started resenting the slot). Mixed days keep the slot interesting enough that I open the laptop without bargaining. Your mileage will vary. If you have a single weak area to crush before a specific interview, focused wins for that cycle. Default to mixed otherwise.

The framework is mine. The content is yours. If coding platforms feel like a chore right now, drop them for this cycle and run quizzes or articles instead. If reading drains you, do the same drill but as videos plus a five-minute written reaction. The roadmap only works if you reach for it without flinching.

What actually happens

You'll miss a day in week two. Probably a Wednesday. You'll feel weirdly guilty about it and consider scrapping the whole plan. Don't. The 2019 stretch I mentioned earlier didn't end because I missed a day, it ended because I missed a day and then decided the whole calendar was broken.

Treat a miss like a typo. Fix it the next morning and keep going. Finishing a 3-4 week cycle, even an imperfect one, puts you ahead of most developers I know who have been promising themselves they'd "start learning seriously" since January.

The next lesson is a real, week-by-week example of one of my own cycles. I want you to see what the calendar looks like in practice before you build yours, including the slot I always end up moving and the one I never touch. See you there.