Why I Built Training Hub
Every course on this site started the same way: I was trying to learn something for work, and the material I could find was written at the wrong altitude. Either it was a five-hundred-page reference manual that assumed I already understood the topic well enough to know which chapters mattered, or it was a fifteen-minute video that got the syntax right and skipped every detail that actually matters once the thing is running in production. There was rarely anything in between.
That gap is oddly consistent across topics. Whether I was learning PostgreSQL replication, trying to actually understand what a Kafka consumer group does under the hood, or figuring out why a Kubernetes pod kept getting OOM-killed, the pattern repeated: excellent official docs that read like a specification, a handful of outdated blog posts, and a lot of Stack Overflow answers that solved someone else's slightly different problem. Nothing walked through the concept, showed a realistic example, and then checked whether I actually understood it before moving on.
The format I kept wishing existed
Training Hub is my attempt to build the resource I kept wishing existed: a course format that treats a technical topic the way a good technical lead would explain it to a new hire. Every lesson follows the same shape on purpose. First, a plain statement of what you should be able to explain or do by the end. Then the actual concept, in enough depth that you understand why something works the way it does, not just what command to type. A worked example grounded in a real scenario. A diagram where a picture genuinely earns its place, not because every lesson needs one. Then review questions that test understanding, not recall of a definition.
Repeating that shape across every lesson, in every course, was a deliberate choice. Once you have read a handful of lessons on this site, you know exactly what to expect from the next one, which means the format gets out of the way and the content can do the work. That consistency also made it possible to build things like a real-time search across every course and lesson, a reading-width control, and a Review Questions accordion once, and have them work identically everywhere, instead of every course page reinventing its own layout.
Why it's free
There is no signup, no paywall, and no email capture anywhere on this site, and that is not an accident or a temporary launch promotion. The material exists because I wanted it to exist, not because it needs to convert into a subscription. Your progress, saved lessons, and reading history are kept entirely in your browser's local storage. Nothing is sent to a server, because there is no account system to send it to.
- No account, no email, no credit card, ever.
- Progress and bookmarks live in your browser only - clear your browser data and you start fresh, which is the honest tradeoff for not tracking you anywhere else.
- Every lesson is also a real, crawlable static page, so it works for search engines and for anyone who just wants to read one lesson without ever "logging in" to anything.
What's actually on here
The catalog covers the topics that come up constantly in backend and infrastructure work: databases from PostgreSQL to MongoDB to Elasticsearch, the messaging and streaming layer with Kafka, the operational layer with Docker, Kubernetes, and observability, the theory underneath distributed systems, and the practical skills around API design, security, and the Linux command line most of us learned by accident rather than on purpose. It keeps growing because the list of things worth understanding deeply never really finishes.
If there's a topic you wish had a course like this and it isn't here yet, that's useful to know. The catalog grows based on exactly that kind of gap.