This is a map of what I'm studying, not a list of credentials. It is meant to change as I go.
Nothing here is claimed as certified or finished. Where a topic is simply open, it says open.
These subjects are not eight separate tracks. Most of them only make sense next to each other.
Understanding how systems break is the fastest way to understand how they work. I care less about breaking things than about the reasoning underneath them.
To fill in
Not written down yet. This section stays empty until there is something real to put in it.
To fill in
Nothing here yet. Only real work gets listed on this page.
The environment most of what I want to understand runs on. Shell, permissions, processes and services are where theory becomes something you can actually see.
To fill in
Not written down yet. This section stays empty until there is something real to put in it.
To fill in
Nothing here yet. Only real work gets listed on this page.
It is the layer where the abstract becomes concrete. Following a packet teaches you more about a system than reading about it does.
To fill in
Not written down yet. This section stays empty until there is something real to put in it.
To fill in
Nothing here yet. Only real work gets listed on this page.
It is the language I reach for first when I want to test an idea quickly, and AI work pulls me back to it constantly.
To fill in
Not written down yet. This section stays empty until there is something real to put in it.
To fill in
Nothing here yet. Only real work gets listed on this page.
Not for its own sake. Mathematics is how I keep a piece of code honest about what it is actually doing.
To fill in
Not written down yet. This section stays empty until there is something real to put in it.
It changed how I write conditions. Reasoning about why a branch must be true or false is closer to writing software than most people expect.
To fill in
Not written down yet. This section stays empty until there is something real to put in it.
I treat it as a subject to understand rather than a tool to advertise. What is actually happening under the interface is the interesting part.
To fill in
Not written down yet. This section stays empty until there is something real to put in it.
To fill in
Nothing here yet. Only real work gets listed on this page.
It sits exactly where creative development and programming meet: a scene is just state, and the renderer is just a function of that state.
To fill in
Not written down yet. This section stays empty until there is something real to put in it.
Understanding how systems break is the fastest way to understand how they work. That holds for a chess rules engine, for a permissions policy in a database, and for a renderer drawing a 3D scene.
So the work follows the same shape every time: build something real, read the source, find the part that surprises you.
