Resources & Tools

System design learning resources (curated for quick reference):

• Designing Data-Intensive Applications (DDIA) - most-endorsed book in the industry
• dev.to/somadevtoo/... - "11 system design books that actually made me a better engineer" (curated list)
• github.com/ashishps1/awesome-system-design-resources
• github.com/donnemartin/system-design-primer
• hyrumslaw.com
• github.com/nginx/nginx - real production load-balancer codebase to study
• AWS ALB docs, Google Cloud HTTPS load balancing docs, NGINX load-balancing docs
• k8sgames.com and kubernetes.io/docs/concepts/architecture/ for Kubernetes fundamentals
• codecrafters.io and learncpp.com for hands-on systems-language projects
• Amazon's Leadership Principles page - directly relevant to Amazon's OA "work style survey"

• Neon (managed Postgres), Vercel, Cloudflare Workers/R2/Pages/KV/Durable Objects, Railway, AWS ECS/EKS, Blacksmith (CI runner), PgBouncer, minikube, Terraform
• Remotion (JS-based programmatic video generation), Whisper (local transcription)
• Claude Code, Claude Desktop, Codex - used together in various role-split configurations; subagents and custom Skills as a favored working paradigm
• Obsidian - used as a long-term personal knowledge base that reportedly pairs unusually well with agentic coding tools
• Fish Audio - mentioned as a free TTS API option (time-limited free-tier promo referenced, may not still be active)

• A podcast focused on context windows and "harness engineering" for agentic coding, shared positively (specific title not given in the source, referenced only via a YouTube link).
• A referenced video on architectural drift in the context of increasing agentic/AI-driven codebase changes - the core question raised: how do you catch a system slowly diverging from its intended design when local tests still pass.
• A LinkedIn post specifically describing the structure of Amazon's new "AI coding assistant" OA round, cross-referenced by an experienced professional experiencing that exact round.

Product naming brainstorm (as the app moved beyond its original working name, "this guide"): the field-suggested alternatives included The Daily Design, System Investigations, Init, Terrarium, Drafting Table, Does It Scale?, Phase Change, Caldera, Secant, Tensile, O(1), Decouple, TechLingo, The Daily System, and System Daily - this document's own source-file naming (Devmaxx) suggests the team ultimately landed on or moved toward that name during the period covered.

End of digest. This document was synthesized from raw reputable industry sources export data across 7 channels (~1,000+ messages total) and organized topically rather than chronologically. Direct participant usernames are preserved for traceability back to source where it matters (e.g., attributing a specific interview writeup or project), but most tactical/strategic advice is presented as consolidated the field knowledge rather than attributed quote-by-quote.