Junior in. Senior out.
Structured paths that take you from writing code to designing systems. System design, low level design and the languages underneath, in plain words, with diagrams you can play with.
See what breaks first.
Tools can write the code. They cannot tell you which design falls over on the busiest day of the year. Drag the traffic up and watch one server turn into a system, one bottleneck at a time.
This is the first chapter in miniature. The real ones go much deeper.
The app, the database and the uploads share one box. It is cheap and simple, and one failure takes all of it down.
Chapter: Scaling from one serverWrite it. Shape it. Scale it.
Three stops, in the order the job teaches them. Every path is numbered, so you always know what comes next and how far you have come.
- 01Write it
A language you can think in, and the tools around it.
- 02Shape it
Classes and modules that survive the next change request.
- 03Scale it
Systems that survive traffic, failure and the busiest day of the year.
- 04Next
Paths that are planned and not written yet.
AI engineeringSoonDistributed systemsSoon
Built to be understood, not memorised.
- 01It starts with a real problem
A QR code at a tea stall. The tatkal rush. A cricket final. Every chapter opens on something you have used.
- 02You answer before you read
Each chapter asks for your call first. Two lines is enough, and nobody else sees it.
- 03The diagrams move
Turn up the load, split the network, add a node, and watch what the design does.
- 04You leave able to say it
A checkpoint, the trade-offs, and a version you can say out loud in 60 seconds.
Or start from a question you have been asked.
Each one is a full chapter: clarify, estimate, draw, then defend the trade-offs the way you would in the room.
All 34 chaptersHighlight it. Note it. Pick it up tomorrow.
Everything you keep stays in this browser. There is no sign up between you and the next chapter.
A cache is a bet that the next read looks like the last one.
Select any sentence to mark it, and add a line on why it matters to you.Start with one server.
The first chapter takes one overloaded machine and works out, step by step, what to change and in which order.
Read the first chapter