Start building
You don't need permission, a perfect stack, or another course. You need one small thing, finished, and put in front of a person.
- You have a 30-day plan and four projects sized to actually finish.
- You know which habits matter and which advice to ignore for now.
Everything in this course is learned by doing, and the doing has a shape: one small project, shipped, then improved. Not a portfolio, not a rewrite of your employer's platform, not a framework you'll switch next month. Something a person can use, that you can deploy, that you can change without fear.
10.1Thirty days, four weeks
| Week | Do | Done looks like |
|---|---|---|
| 1 | Set up the repo from module 02. Build the smallest possible version — one screen, one action, hard-coded data. | A clean clone runs with one command; first commits exist |
| 2 | Add the one real rule your app needs (a calculation, a filter, a permission) and three tests around it. | The rule is isolated, tested, and readable in one function |
| 3 | Deploy it. CI on push, a real URL, a smoke test of the core journey. Fix whatever the deploy exposes. | Someone else can open it on their phone |
| 4 | Give it to one person. Watch them use it without helping. Fix the first thing they get wrong. | One real user, one real fix, a README that explains it |
10.2Four projects sized to finish
1 · The thing you already do by hand
Renaming files, reconciling a spreadsheet, formatting a report. A 60-line script with a CLI flag and two tests. Deploy: run it on a schedule.
1 weekend · teaches scripts, tests, cron
2 · A single-purpose web app
One list, one form, one rule. A shift rota, a reading log, a quote tracker. Deploy: one container on a small host.
2 weekends · teaches CRUD, auth, deploy
3 · A CLI tool for a real annoyance
Wrap an API, parse a file, check a condition. Ship it as a single binary or a package. Deploy: your own PATH, then a friend's.
1–2 weekends · teaches I/O, errors, packaging
4 · An automation with a schedule
Something that runs without you: a digest, a monitor, a reminder. Deploy: a cron job with logging and a failure email.
1 weekend · teaches reliability, secrets
Pick one. The test is not whether it's impressive — it's whether you would use it, which is what keeps you interested long enough to finish. Finishing is the skill nobody teaches and every employer notices.
10.3Habits that make the difference
- Commit every working session, even if the session was twenty minutes. History is a habit before it is a tool.
- Write the test when you fix a bug. It's the cheapest documentation you'll ever produce.
- Keep the README honest. Three sections, updated when they stop being true.
- Deploy early. The first deploy teaches you more about your design than a week of local coding.
- Keep a log of what broke and what you learned. After a year it's the most valuable file in the project.
- Read your own diff before asking anyone else to. You'll catch half the issues yourself.
10.4What to ignore, for now
- Microservices and Kubernetes. One process on one machine can serve a surprising number of people, and it is debuggable by one person.
- 100% coverage. Test the rules and the edges; don't chase a number.
- Framework churn. Pick one, learn it properly, ship. The concepts transfer; the syntax doesn't matter as much as you think.
- Certifications. Nobody has ever asked to see one before letting someone build something useful.
- Other people's architecture. Copy the principles, not the shape — they had different constraints.
You will feel like an impostor for a while. Everyone does, including the people whose code you admire — they are just further along the same loop, with more scar tissue and better habits. The gap between you and them is not talent; it's the number of small things you have shipped and fixed. That number starts at zero for everyone, and the only way it grows is by starting something today that is embarrassingly small. Small, finished, and used beats ambitious, abandoned, and impressive.
What is the best first project after this course?
60-second recap
- Four weeks: make it run, add the rule and its tests, deploy it, watch one person use it.
- Pick something you'd use. Interest is what gets a project finished.
- Commit, test, README, deploy early, keep a log. Boring habits, compounding returns.
- Ignore the noise. One process, one framework, real users.