Distributed Transactions
Listed inDistributed TransactionsDistributed Systemson
Sagas, compensating actions, and the outbox pattern for writing to a database and a queue at once.
Advanced10 minDraft
#correctness
Page 15 of 18
Listed inDistributed TransactionsDistributed Systemson
Sagas, compensating actions, and the outbox pattern for writing to a database and a queue at once.
Listed inDesign an Ad Click AggregatorSystem Design Questionson
High-volume event ingest, windowed aggregation, late-arriving data, and exactly-once counting.
Listed inPrivacy and Data HandlingSecurityon
Data minimisation, retention, PII in logs, and deletion that actually deletes.
Listed inEngineer vs ProgrammerIntroductionon
Where writing code ends and engineering begins: constraints, trade-offs, and responsibility for the result.
Listed inGoProgramming Languageson
A deliberately small language with fast builds and cheap concurrency, designed so a large team can read anyone else’s code.
Listed inMinimum Spanning TreesData Structures & Algorithmson
Kruskal and Prim, and the clustering and network-layout problems that turn out to be MST in disguise.
Listed inComments and DocumentationCode Crafton
Comment the why, not the what — and the handful of cases where the what genuinely needs saying.
Listed inThe DOM and EventsFrontend Engineeringon
Capture, bubble, delegation, and why touching the DOM in a loop is the slowest thing on the page.
Listed inQuery PlansDatabaseson
Reading EXPLAIN, spotting the sequential scan that matters, and fixing statistics rather than guessing.
Listed inCommunicating a DesignSystem Designon
Drawing the diagram that survives review: components, data flow, and the trade-offs written down beside it.
Listed inMocks, Stubs, and FakesTestingon
The five kinds of double, when each is right, and the mock-heavy test that verifies nothing.
Listed inCapacity PlanningObservability & Operationson
Load testing, headroom, autoscaling limits, and the dependency that does not scale with you.
Listed inProgramming ParadigmsLanguages & Type Systemson
Imperative, object-oriented, and functional styles as tools rather than tribes.
Listed inAssemblyProgramming Languageson
Rarely written, occasionally read — when the profiler or the debugger drops you to instructions and you have to follow.
Listed inThe Git Object ModelVersion Controlon
Blobs, trees, commits, and refs — the four objects that make every other command obvious.
Listed inAPI DesignAPIs & Protocolson
Naming, granularity, consistency, and designing the error responses before the happy path.
Listed inKeyboard NavigationAccessibilityon
Tab order, skip links, and the rule that anything clickable must be reachable and operable without a mouse.
Listed inWhat System Design IsSystem Designon
Choosing between architectures under constraints you were given, rather than inventing anything new.
Listed inConcurrency vs ParallelismConcurrency & Performanceon
Structuring for overlap versus actually running simultaneously, and which problem you have.
Listed inContinuous DeliveryBuild, CI & Deploymenton
Every commit deployable, decoupling deploy from release, and the batch size that makes it safe.