Chapter 2 of 7 · 5 checks · 3 min
Build a learning plan you can keep
A plan that fits around your current life beats an ambitious plan you abandon in week three.
Pick one structured curriculum and follow it to the endMust
Why it matters and how to check
Jumping between tutorials is the most common way switchers lose time. Pick one well-maintained path for your direction and finish it. Good free options include MDN's Learn web development (written to take learners from beginner to comfortable), Harvard's CS50, which says most of its students have never taken computer science before, and The Odin Project, a free open source full stack curriculum built around projects.
Use other resources to fill gaps, not to restart.
Check it: you have named one main curriculum and you are tracking your progress through it.
Do
- Write down the one curriculum you are following
Avoid
- Starting a new course each time one gets hard
Set fixed weekly study hours that fit your real lifeMust
Why it matters and how to check
Decide when you will study each week: specific evenings, early mornings or weekend blocks. Protect those hours like appointments. Consistency over months matters more than long sessions now and then.
Be realistic about work, family and energy. A plan of a few steady hours a week that you keep beats a plan of many hours that you abandon.
Check it: your weekly study hours are in your calendar and you have kept them for at least four weeks.
Do
- Put study blocks in your calendar
Avoid
- Planning study only "whenever I have time"
Learn the fundamentals before chasing frameworksMust
Why it matters and how to check
For almost every direction, the foundations are the same: one programming language well, how the web or your platform works, Git and the command line, reading error messages, and breaking a problem into steps. Frameworks change; these do not.
Once the basics are steady, learn the main framework or tool that shows up in your target listings.
Check it: you can build a small program in your main language without following a tutorial step by step, and you use Git for all your work.
Do
- Use Git from the first week
Avoid
- Learning three frameworks before one language
Keep notes and track what you have learnedNice to have
Why it matters and how to check
Write short notes after each session: what you learned, what confused you, and what you would try next. Over months, these notes become your own reference and show you how far you have come on slow weeks.
Some switchers publish short posts about what they learn. That is optional, but it helps people find you later.
Check it: you have notes for most study sessions and can look back at what you learned each month.
Do
- Write three lines after every session
Avoid
- Relying on memory for things you will need again
Have a routine for getting unstuckShould
Why it matters and how to check
Everyone gets stuck. Decide in advance how long you will try alone (for example, an hour), then read the docs, search the exact error message, and then ask in a community such as your curriculum's forum or Discord, with your code, the error and what you tried.
Getting unstuck is itself a skill developers use every day.
Check it: when you are stuck, you follow a set routine and ask clear questions with code and error messages.
Do
- Include the exact error and what you tried when asking for help
Avoid
- Staying stuck on one problem for days without asking