All paths
21 paths
Role paths 3
What a role needs to know, in the order it needs it.
- Not startedBackend engineer: from a request to a service you can runWhat a backend engineer works with every day: the runtime under the service, a request's path through the framework, the database connections and transactions it borrows, the tests that prove it works across boundaries, and what changes when a language model is one of your dependencies.18 topics · Intermediate
- Not startedFrontend engineer: from JavaScript to a fast, accessible pageWhat a frontend engineer needs underneath the framework: how JavaScript runs, how the browser turns your code into pixels and events, what makes a page accessible, fast and safe, and how to test the journeys that matter.17 topics · Intermediate
- Not startedMobile engineer: iOS and Android, side by sideThe rules both mobile platforms impose on your app, learned in pairs: a life cycle you don't control, one thread that draws, structured concurrency, declarative UI, strict limits on background work, push through the platform's own service, and a store between you and your users.17 topics · Intermediate
Skill paths 8
How a language, runtime or tool really works, one topic at a time.
- Not startedAI engineering: building with large language modelsHow to put a language model inside real software: what it actually computes, how to ask for output your code can trust, how to give it tools and documents, how to test it, and how to keep it fast, affordable and safe.12 topics · Intermediate
- Not startedAndroid: how an app really runsWhat the system does with your app once it is installed: the process it may kill at any time, the one thread that draws, how Compose redraws, where state survives, and how work, data, pushes and builds fit around that.12 topics · Intermediate
- Not startediOS: how an app really runsWhat iOS does with your app between launch and being killed: states, the main thread, how SwiftUI redraws, memory, Swift concurrency, and the rules for networking, storage, background work, push and shipping.11 topics · Intermediate
- Not startedJava: how the JVM runs your codeWhat happens after javac: bytecode, class loading, the JIT, the heap and its collectors, and how threads (platform and virtual) see each other's writes.12 topics · Intermediate
- Not startedJavaScript: how it really runsWhat the engine actually does with your code, from the call stack to the event loop, one picture at a time.12 topics · Intermediate
- Not startedNode.js: how the server side runsWhat happens between your JavaScript and the operating system: the loop's phases, its private queues, the thread pool, streams, and threads of your own.8 topics · Intermediate
- Not startedQA automation: tests that catch real bugsDecide what is worth testing and at which layer, write tests that fail for real bugs and only for real bugs, and keep a growing suite fast and trusted from the first unit test to production.12 topics · Intermediate
- Not startedSpring Boot: how a request becomes a responseWhat Spring Boot does between an HTTP request arriving and a response leaving: the container that builds your objects, the proxies that wrap them, the threads, transactions and connections each request borrows, and how to see and test it all.12 topics · Intermediate
System design paths 10
Short routes through the library's pattern walkthroughs.
- Not startedResilience 101Keep one failing dependency from taking everything down.4 topics
- Not startedConsistency across servicesChange data in more than one place without losing or doubling anything.5 topics
- Not startedScaling outSpread load across many machines and keep them from drowning.5 topics
- Not startedEvent-driven systemsLet services react to what happened, and make long processes finish.6 topics
- Not startedAPIs and the edgeShape what clients see, and keep the contract honest as both sides change.7 topics
- Not startedFast readsServe the same answer cheaply, close to the reader, without serving it wrong.3 topics
- Not startedEvolving a system safelyReplace and change running systems without a big-bang rewrite.4 topics
- Not startedStaying up at scaleContain failures so most users never notice them.4 topics
- Not startedInside the databaseHow databases stay durable, scale reads, and share their changes.4 topics
- Not startedCoordinating servicesGet several machines to agree, take turns, or commit together.4 topics