CS Fundamentals
Every bound derived. Every structure shown working. Every failure mode named.
Sections
Section titled “Sections”- 📈 ComplexityHow to reason about cost — deriving bounds rather than memorising them, and knowing when the constant factor beats the exponent.
- 🧱 Data StructuresThe shapes data takes in memory, what each one buys you, and — the part usually left out — what each one costs you.
- ⚙️ AlgorithmsSorting, searching, and traversal — with the comparison counter running, so the complexity is a number you watch rather than a claim you accept.
- 🧩 ParadigmsDivide and conquer, greedy, dynamic programming, backtracking — the recognisable shapes of a solution, and how to tell which one a problem is asking for.
- 🛰️ SystemsWhat happens once the code leaves your laptop — event loops, message brokers, databases, caching, APIs, and testing.
- 🔤 Languages & DesignTypeScript's type system, the Node runtime, and the design vocabulary — SOLID, patterns, and the caveats that keep them from becoming dogma.
- 🗄️ Data EngineeringGetting data from where it is to where it is useful — SQL, modelling, pipelines, and the quality checks that catch a bad load before a dashboard does.
- 💾 Databases & StorageRelational, document, and vector stores — what each one indexes, what it charges you for, and the query plan that tells you which one you actually got.
- ☁️ Cloud & InfrastructureRunning software you cannot reach with your hands — the three clouds, Terraform, containers, CI/CD, and knowing what it costs before the invoice says so.
- 🤖 AI EngineeringBuilding on models that are probabilistic by construction — embeddings, retrieval, agents, and the evaluation discipline that separates a demo from a system.
- 🖥️ Web & FrontendWhat the browser actually does with your code — rendering strategies across React, Vue, Svelte, Astro and Next, and the performance budget each one spends.
- 🔌 Backend & APIsThe server side — Node, Nest and Python, REST and GraphQL, authentication, background work, and the failure modes that only appear under concurrency.
- 🏛️ ArchitectureDecisions that are expensive to reverse — distributed systems, event-driven design, resilience, and how to reason about a system before it exists.
- 🚨 Production EngineeringWhat it looks like to actually operate a system — reading a symptom, running an investigation with real evidence, and knowing which failure mode produces which signature.