Skip to main content

Chapter 12 — Real-World References, Case Studies, and Resources

Engineering Blogs, Books, Certifications, and Where to Go Next

The best architects are also the best readers.


12.1 Engineering Blogs Worth Following

These are primary sources — direct reports from engineers who solved the problems at scale, not summaries or interpretations.

Company / AuthorBlog URLWhat to Read First
Meta Engineeringengineering.fb.com"Building the New Facebook.com" — RSC before RSC existed
Instagraminstagram-engineering.com"Making Instagram.com Faster" (3-part series)
Airbnbmedium.com/airbnb-engineering"Hypernova: Server-Side Rendering for React Apps"
Netflixnetflixtechblog.com"Rebuilding the Netflix Homepage" — performance at scale
Shopifyshopify.engineering"How We Built Hydrogen" — RSC in production
Vercelvercel.com/blogTurbopack and Next.js announcements — primary source
GitHubgithub.blog/engineering"Primer: GitHub's Design System"
Linearlinear.app/blog/engineering"How Linear Builds Product" — offline-first patterns
Figmafigma.com/blog/engineering"How Figma's Multiplayer Technology Works" — CRDT
Discorddiscord.com/blog/engineering"How Discord Stores Billions of Messages"
Atlassianatlassian.com/engineeringTeam topology and scale articles
Dan Abramovoverreacted.io"A Complete Guide to useEffect" — still the best
Kent C. Doddskentcdodds.com/blogTesting Trophy, Epic React explanations
Josh W. Comeaujoshwcomeau.comCSS animations, React deep dives
Tanya Reillynoidea.dogStaff engineer archetypes, "Radiating Intent"
Alex Russellinfrequently.orgPerformance, mobile web — honest and uncomfortable
Addy Osmaniaddyosmani.com"Learning Patterns" — architectural patterns for JS

12.2 Essential Books — Ranked by Stage

For Senior Engineers (Stage 3)

BookAuthor(s)What You Get
JavaScript: The Good PartsDouglas CrockfordThe mental model of JS at its core
You Don't Know JS (series)Kyle SimpsonClosures, prototypes, async — deep
Clean CodeRobert C. MartinCode quality principles (adapt, don't copy)
The Pragmatic ProgrammerHunt, ThomasCraft of software development
A Philosophy of Software DesignJohn OusterhoutComplexity vs simplicity trade-offs

For Tech Leads and Architects (Stage 4–5)

BookAuthor(s)What You Get
Staff EngineerWill LarsonThe IC architect career path — essential
The Staff Engineer's PathTanya ReillyBig-picture thinking, execution, leveling up
Building Evolutionary ArchitecturesFord, Parsons, KuaFitness functions, evolutionary design
Fundamentals of Software ArchitectureRichards, FordPatterns, styles, trade-off analysis
Building Micro-FrontendsLuca MezzaliraDefinitive reference — the author invented the pattern
Team TopologiesSkelton, PaisCognitive load, team types, interaction modes
Designing Data-Intensive ApplicationsMartin KleppmannCRDTs, distributed systems — heavy but worth it
The Manager's PathCamille FournierEngineering ladders, growth paths
Radical CandorKim ScottLeadership communication — practical
An Elegant PuzzleWill LarsonEngineering management systems

For System Design and Architecture Documentation

BookAuthor(s)What You Get
Software Architecture PatternsMark RichardsQuick overview of 5 key patterns
arc42 by ExampleHruschka, Starkearc42 template with worked examples
The C4 Model (online)Simon BrownFree book at c4model.com
Domain-Driven DesignEric EvansThe original DDD reference (dense but canonical)
Implementing Domain-Driven DesignVaughn VernonMore accessible DDD for practitioners

12.3 Online Learning and Practice

ResourceTypeBest For
greatfrontend.comPractice platformRADIO framework, 500+ questions, system design
frontendmasters.comVideo coursesDeep dives: React, TypeScript, performance
web.dev/learnFree textPerformance, Core Web Vitals, PWA
javascript.infoFree textModern JS from scratch — the best free JS book
typescript-exercises.github.ioPracticeTypeScript type system challenges
excalidraw.comToolFree whiteboard for system design diagrams
mermaid.liveToolDiagrams as code, renders in GitHub/GitLab
bundlephobia.comToolBundle cost of any npm package
c4model.comFreeC4 model documentation and tooling
feature-sliced.designFreeFSD methodology, examples, ESLint plugin
storybook.js.orgToolComponent documentation and visual testing

12.4 Certifications Relevant in Germany and Europe

Germany and the DACH region specifically value formal certifications alongside practical experience. These credentials are recognized in job postings at companies like Kärcher, Bosch, SAP, and Deutsche Telekom.

CertificationIssuerRelevance
iSAQB CPSA-FiSAQB (Germany)Foundation software architecture — most recognized in German enterprise
iSAQB WEB moduleiSAQBWeb-specific architecture patterns
iSAQB FLEX moduleiSAQBAgile and evolutionary architecture
AWS Solutions Architect AssociateAWSCloud infrastructure knowledge
Google Cloud Professional ArchitectGoogleAlternative cloud path
Certified Kubernetes Application Developer (CKAD)CNCFContainer/deployment knowledge
MongoDB Associate DeveloperMongoDBDatabase design patterns

Note on iSAQB: Kai Intelmann (Kärcher) is iSAQB certified. The iSAQB CPSA-F covers arc42, ADRs, quality attributes (which map directly to ISO 25010), and formal trade-off analysis — directly relevant to Kärcher's architecture practices.


12.5 Conferences and Community

EventFocusLocation
JSConf EUJavaScript at scaleEurope (rotating)
ReactConfReact ecosystemOnline + USA
Frontend NationFrontend breadthOnline
EuroRustTooling trends (Turbopack, SWC, Biome)Europe
QCon LondonArchitecture + engineering leadershipLondon
Software Architecture SummitFormal architectureGermany/DACH
iSAQB Software Architecture GatheringADRs, arc42Germany

German-language communities:

  • software-architektur.tv — Stefan Tilkov and colleagues on architecture (German + English)
  • heise Developer — German tech journalism with architecture focus
  • INNOQ blog — strong on DDD, microservices, architecture patterns

Development:
Vite: vitejs.dev
Next.js: nextjs.org/docs
TypeScript: typescriptlang.org/docs
Tailwind CSS v4: tailwindcss.com

State and Data:
TanStack Query: tanstack.com/query
Zustand: zustand.docs.pmnd.rs
React Hook Form: react-hook-form.com
Zod: zod.dev

Testing:
Vitest: vitest.dev
Playwright: playwright.dev
MSW: mswjs.io
Testing Library: testing-library.com

Architecture Tools:
FSD: feature-sliced.design
Nx: nx.dev
Turborepo: turbo.build
Madge (circular): github.com/pahen/madge
Log4brains (ADRs): github.com/thomvaill/log4brains

Performance:
Lighthouse CI: github.com/GoogleChrome/lighthouse-ci
Bundlewatch: bundlewatch.io
web-vitals: github.com/GoogleChrome/web-vitals

Security:
DOMPurify: github.com/cure53/DOMPurify
OWASP Top 10: owasp.org/www-project-top-ten
CSP Evaluator: csp-evaluator.withgoogle.com

Chapter 12 Summary

You now have a complete map of where to go to keep growing:

For daily learning, follow 3–5 engineering blogs consistently. The Meta, Netflix, and Figma engineering blogs publish architecture-level thinking that no course or book matches for relevance.

For career growth, read "Staff Engineer" (Larson) and "The Staff Engineer's Path" (Reilly) before your next performance review conversation.

For interview preparation, practice on greatfrontend.com using the RADIO framework with a timer. Draw system design diagrams on Excalidraw until diagramming becomes second nature.

For certification in the German market, the iSAQB CPSA-F is the highest-signal credential. The curriculum aligns directly with arc42, ADRs, quality attributes, and ATAM — all covered in this book.


End of The Complete Frontend Architect Book — Chapters 1–12

Continue to: