Curriculum — The Hashflag Method - Vets Who Code

New Cohort Starts: Apr 05, 2027
A syllabus tells you what comes next. It can’t tell you why. Ours is a map of 375 ideas and the 529 places they hold each other up — so before a veteran writes a line of code, they can see the whole route, where they already stand on it, and what every step is load-bearing for.
Selecting a dot lights everything the idea rests on and prints the written reason for each link. Depth runs top to bottom: a concept sits below whatever holds it up. Nothing here gates you — it maps what a skill is made of.
Rendering all 375 micro-topics and 529 prerequisite links of Hashflag Graph v2.3 — 435 load-bearing, 94 supporting, across 8 subjects and 53 domains.
Someone shows up having run Linux boxes for ten years and never touched JavaScript. Someone else has written Python scripts for a shop that didn’t call it engineering. Both of them can find themselves on this map on day one — not at week one of a course, but at the actual edge of what they already hold.
Then they walk the whole thing. Every veteran in a cohort covers all 375 ideas in 17 weeks, because the graph tells us exactly how much has to sit under each one, and nothing gets taught before its foundation exists.
Here’s the map by the numbers.
One teachable idea each. Not a chapter — an idea.
435 that carry weight, 94 that smooth the way.
Grouped into 8 subjects.
35 places to start. 170 places to finish.
Nothing is its own prerequisite. We check.
Most curricula only ever answer the last one. Here's all four, and who makes each call.
We look at what employers are actually paying people to do — Lightcast demand data, O*NET, BLS wages — and let that decide what belongs on the map. When the market moves, we rebuild behind it. Nobody here teaches a thing because we happen to know it.
We broke every concept down to a single teachable idea and wired it to what it stands on. The order isn't a judgment call and it isn't a table of contents — it falls out of the map. If we can't say what an idea rests on, it isn't ready to teach.
Every idea gets met three times, with less help each time: we show it, then you do it with a spotter, then you do it alone. Educators call this Gradual Release of Responsibility. Every veteran we've ever trained already knows it by the other name.
Nothing gets checked off because a video ended. Each idea names the thing you have to produce and the standard it gets judged against. You built it and it meets the criterion, or you're not done. Trained to standard, or not trained.
A line on this map isn't decoration. It's a claim about what holds what up, and every one of them carries the sentence explaining it.
Solid arrowed lineLoad-bearing — solid, arrowed
Retrieval has nothing to search until the vectors exist. Teach it the other way around and the second idea is standing on air.
Dashed lineSupporting — dashed, open
You can build the pipeline without it. You just won’t know whether it works.
Every one of the 529 links has a sentence like that behind it. If we couldn’t write the reason, the link didn’t go in.
This is the level every one of the 375 is specified to — written before the lesson, not after.
Node T20 · sample record
Measure generation faithfulness
The line that matters is the evidence criterion. It’s the difference between a veteran who watched a lesson on measuring faithfulness and one who built a check that caught a fabricated answer. The first is a completion. The second is something a hiring manager can look at.
Type tells an instructor how to teach it. Exit depth tells them how much help to take away. Market anchor is the reason it’s on the map at all — the receipt that says an employer is paying for this.
Tap any dot above to read the same record.
Subjects say what an idea is about. They don't say when you meet it — the links decide that, and a single subject can run the entire length of the map. Testing shows up early and never stops. So does version control.
57 topics · 10 domains
30 topics · 6 domains
49 topics · 7 domains
61 topics · 4 domains
25 topics · 4 domains
29 topics · 5 domains
58 topics · 7 domains
66 topics · 10 domains
A veteran who's run Linux for a decade shouldn't sit through week one of the command line. The map already knows what that decade covers and what it reaches, so we start them at the edge of it instead of the beginning of everything.
Take a real posting, name the ideas it asks for, and the map returns the set that reaches them and the order they have to come in. Not “learn React” — the eleven things under React that make React make sense.