Part III — Beyond the Stack

The stack changes every two years. These skills don't.

If you've shipped a few production projects and you're starting to ask "why am I always relearning the same lessons in different syntax?" — that's the signal that the leverage has moved from more frameworks to more fundamentals.

The career inflection point

Junior developers are graded on whether their code works. Mid-level developers are graded on whether their code is the right code for the situation. The foundations in this part are how you make that shift — they're what lets you judge whether a solution fits a problem, instead of just picking the first one that compiles.

What's in this part

• Computer-science fundamentals — Big-O, data structures, algorithms, concurrency. The vocabulary every senior engineer uses without thinking.
• Engineering judgment — Knowing what not to build. Boring tech, reversibility, the cost of inaction. Pairs with Chapter 15: Decisions.
• Systems thinking — How a system behaves under load, failure, and time. Latency, throughput, queues, backpressure, idempotency.
• Security beyond HTTPS — Threat models, OWASP top 10, secrets handling, supply-chain risk. The class of bugs that ship to production unless you're explicitly looking for them.
• Testing, properly — The pyramid vs the trophy, testing behavior not implementation, the over-mocking trap, and why flaky tests are bugs. Pairs with Testing (Foundations).
• Git beyond the basics — Git as a commit DAG: rebase vs merge, the reflog safety net, bisect, and the three resets. Pairs with Stage 4: Git.
• Performance engineering — Profile before optimizing, the latency numbers, Core Web Vitals, the database bottleneck, and caching as the biggest lever. Pairs with Performance (Foundations).

How to read this part

Slowly. None of these are crash courses — each one is a multi-year skill. The page for each is a curated entry point: what to read, what to practice, what milestones tell you you've internalized it.