Why we start with Nix
The reasons Nix is hard to learn are exactly the reasons it is the right place to begin.
Picking a first course is picking a thesis. Ours is that if we can teach Nix well, we can teach the rest of the systems stack — because Nix is hard for all the reasons the rest of the stack is hard, concentrated in one tool.
The difficulty is the point
Nix touches shells, package management, build systems, and OS internals at once. Its documentation is terse for a newcomer. Community knowledge is fragmented across a decade of forum threads. There is no obvious path from "I installed it" to "I'm fluent."
That combination is miserable to learn alone and ideal to learn inside an environment built for it: real machines, instant and reversible failure, and a validator that checks what your system actually looks like rather than what you typed.
Downward from here
After Nix, the direction is down — into the systems layer the cloud-native lab platforms don't touch. They stop where the cloud starts. This one is meant to go the other way: how fast and how far depends on what people want next.
The work is the same whether it's your first week or your fifteenth year: build judgment in an environment designed for it, where the mistake is the trigger and the fix is the lesson.