Tutorial to Engineer
Stop following along.
A short, free course on how to actually learn. Why tutorials fail, what people believe that isn’t true, and a simple loop that puts things in your head — including how to use AI without dulling your own thinking.
No signup. Finishable in a weekend.
If any of this sounds familiar
You don’t need another tutorial.
You need to learn differently.
- You finished a 12-hour course last month and you can’t recall a single thing from it.
- You ship features with AI in minutes and feel a quiet nausea about not understanding the code you just merged.
- You’ve told yourself you’ll rebuild things “from scratch later” for a year. The list of “laters” just gets longer.
- You’re convinced you have to “learn the basics first” before you start the real thing. Six months in, you’re still on the basics.
- You look at a senior engineer and assume it’s talent. It’s not. It’s a different way of practicing.
None of this is a talent problem. It’s a method problem. The good news is the fix is small, plain, and you can start using it tomorrow.
What you walk away with
After a weekend of reading:
Chapter 1
A clear diagnosis of why your last learning attempt didn't stick
Chapter 2
The four myths that have been quietly costing you years
Chapter 3
A simple five-step loop you can apply to anything
Chapter 4
A clear rule for when to use AI and when to turn it off
Chapter 5
The starter vocabulary for naming code that feels wrong
Chapter 6
A way to know your practice is working, even on plateaus
Throughout
One concrete thing to try in your next session
Throughout
A view of what 'getting better' actually looks like
This isn’t a course about a specific language or framework. It’s a course about the operating system underneath all of them — the way you spend your time when you’re trying to get better. Get that right and every framework you ever learn gets cheaper.
Syllabus
7 chapters · 28 units
Every unit is short and dense. One idea per page. One reflection prompt where the idea meets your actual work.
Ch 0Start herePsychological2 units
What this is. Why it's free. Whether to keep reading.
Ch 1Why tutorials failPsychological4 units
Completing a tutorial isn't learning. The feeling of progress and the fact of progress are different things.
Ch 2Common misunderstandingsMedium4 units
Things people repeat at each other, that turn out not to be true.
Ch 3The way to learnPEAK5 units
One loop. Five steps. The simplest version of the thing that actually works.
Ch 4Learning with AIMedium5 units
Use AI as your teacher. Never as your hands. The difference is everything.
Ch 5Building tasteMedium5 units
Taste is recognizing what's going to hurt you later. You build it by reading other people's code.
Ch 6Keeping it goingPsychological3 units
How you sustain a learning practice for years without burning out.
The format
A philosophy course, not a how-to.
Most “learn to code” resources tell you what to build this week. This one tells you how to spend any week. It’s short on purpose — you read it once, then it changes the shape of every tutorial, video, and AI session that comes after.
| Typical “how I learned to code” post | This course | |
|---|---|---|
| Format | Listicle or video essay | 28 short written units |
| What it teaches | A specific stack or roadmap | How to learn anything |
| Voice | Motivational, grindset | Diagnostic, plain language |
| Time to first useful idea | 8 min of intro | Two minutes |
| When it goes out of date | Whenever the stack changes | Never — the principles outlast frameworks |
| What you do with it | Maybe start a course you don't finish | Apply one habit to your next learning session |
Every unit, three beats
- 1. The idea.One durable claim, stated plainly. No jargon you don’t need.
- 2. Why it’s true. The mechanism, not just the assertion. So you can judge edge cases yourself.
- 3. Try it. One small reflection or action you can apply to your own work today.
7 chapters · 28units · ~3–6 minutes per unit.
Open to read
No catch. No signup. No email drip.
- ✓All 7 chapters, 28 units, every reflection prompt
- ✓No signup wall. Open the first unit and read.
- ✓No upsell at the end. No popup. No drip.
- ✓Progress tracking and a continue-learning button, locally on your device
The only honest version of this course is a free one. Read it, ignore it, or mail it to your team — there’s nothing to buy at the end of it.
Frequent objections
Honest answers.
Why is this free?
Because gating philosophy is hypocritical when the whole argument is 'do the work yourself.' Charging for the diagnosis would just be a tax on the people most likely to try it. Read it, share it, or close the tab — whatever you want.
Is this just complaining about tutorials?
No. The first two chapters diagnose what's broken about the way most people learn. Chapter 3 is the positive replacement — a five-step loop you can apply to anything, stated plainly, in one page. The remaining three chapters apply that loop to working with AI, to building engineering taste, and to keeping the whole practice going over years.
Will this teach me to code?
No. This course is one level above 'how to code' — it's how to learn to code (or anything else technical) without wasting years. If you want a course that teaches you to code, try Blank to Browser. If you want a course that teaches you to ship software you can actually explain, try Prompt to Production. This course makes both of those work better.
I already know how to learn. Is this for me?
Maybe not. Unit 0.1 is literally 'the whole course in five bullets' — read those, and if all five feel obvious to you and you already act on them, close the tab. You're the person this course was written by, not for. We respect your time more than we want your engagement.
How long does this take?
About 2–3 hours of total reading if you push through, or one unit a day for a month if you let it land. The units are short on purpose. You don't need to read it in one sitting; the loop is small enough that you can apply it after one chapter and come back to the rest.
Is there a community / support?
No. This isn't a hand-holding course; it's a short read with reflection prompts. The whole point is for you to apply the ideas to your own work, in your own context. If you want a course with feedback and rubrics, the paid courses have those (within the course itself, not as a Slack community).
Will this stay relevant?
Yes. The course deliberately doesn't mention specific years, models, or hot framework names — because principles outlast tooling, and tooling-stamped content rots within months. The ideas about how the brain encodes, why prediction matters, what taste is, and how to use AI without dulling your thinking will be just as true in five years as they are now.
Why no video?
Because video is the wrong medium for this content. The whole course is about how passive consumption doesn't teach you anything. Video would be hypocritical. Text is searchable, skimmable, re-readable in 30 seconds, and forces you to do the work of mental construction yourself — which is the point.
The first unit is two minutes.
Read it. If it doesn’t change how you think about your next tutorial, close the tab and forget you came. If it does — you have a long weekend of reading ahead, and a different way of working on the other side.