You like writing code. This is a map of the routes you can take through that — each one changes what your code can survive, and a little of who you are as the person who wrote it.
cyo is a choose-your-own-adventure for your craft. It is not a ranking of
tools, and there are no "levels" — nothing here says you are on a low rung and
should climb. Every route is a peer choice. You are already a coder who enjoys
this; the question is only which adventure you feel like having next, and what
you want your code to be able to withstand when it does.
A route is worth taking when something genuinely nags at you, or when you want to grow in a particular direction — not because a list told you your stack was wrong. Your stack got you here. These are the next doors, not a verdict on the last one.
./cyo.sh <route>| Route | The adventure |
|---|---|
scripts |
The Federation — keep your dialect, share a proven core |
js |
Faster feet for the JavaScript/TypeScript world |
python |
Provisioning a clean Python expedition |
rust |
Sharpening an already-sharp blade |
spark |
The Paladin — oaths and an aegis of proof |
logic |
Wizardry — relational magic and neuro-symbolic study |
cpp |
The Artificer — reforging the C/C++ toolchain |
git |
The Chronicler — mastering your own history |
fatigue |
The long quest — growing without betraying your guild |
Each chapter ends by pointing at the chapters it opens onto. Wander.
- You enjoy the craft. Nothing here is framed as escaping something bad.
- Identity over hierarchy. A route is an aspect of who you want to be as a builder, not a tier you have or haven't reached.
- Battle-ready is the destination. Every chapter is honest about what your code can now survive — scale, adversaries, time, regulation — and about what the route costs and how reversible it is.
- No fads sold as fixes. Where a route involves something young, it says so.
See PHILOSOPHY.adoc for the reasoning behind the map.
