Tag
Kent C. Dodds discusses moving away from traditional code diffs toward AI-generated visual system recaps that show how the whole system changed, based on primitives and agent-generated summaries.
A tweet from @venkateshdotdev listing 10 challenging system design interview questions covering URL shorteners, scaling, consistency, rate limiting, fault tolerance, and handling traffic spikes.
A quick explainer from @systemdesignone teaching how Amazon Lambda works, likely with a visual aid or walkthrough.
A deep dive into vLLM's architecture and components for high-throughput LLM inference, covering scheduling, paged attention, continuous batching, advanced features, scaling, serving, and benchmarking.
A curated stack of 20 books across 5 categories for learning AI/ML from fundamentals to production systems.
A tweet compiling engineering blogs from 40 top tech companies for learning system design and architecture from real-world production playbooks.
An engineer reflects on repeatedly building webhook integration systems, detailing the hidden complexity of signature verification, deduplication, buffering, and reconciliation crons, and argues that webhook notifications are not a reliable substitute for a complete ordered data log.
The article provides a detailed breakdown of OpenAI's complete software engineer interview process, analyzing round by round the core evaluation points behind initial screening, coding, system design, take-home projects, and the final interview, and compiles them into a systematic engineer advancement checklist.
JavaGuide is a practical open-source GitHub repository for Java backend interview preparation, covering core Java, system design, and common interview questions.
Explores how to quantify the contribution of each latency percentile to mean latency using the Lorenz curve, and connects it to concurrency via Little's law, demonstrating that tail latency often dominates cost and capacity.
An essay analyzing the limitations of single feedback loops in AI agent development, illustrated by a cautionary tale of a support team whose bot's metric optimization led to customer loss, and advocating for a graph-engineering approach that considers multiple interconnected loops.
Kent C. Dodds shares an article and YouTube video arguing that the quality of AI agent outputs depends on the design of system primitives—providing agents with well-crafted, composable building blocks narrows their action space and yields reliable results.
The author explains the differences between SSO, OAuth, OIDC, and SAML, clarifying that SSO is a user experience, OAuth is for authorization, OIDC provides identity on top of OAuth, and SAML is an older enterprise protocol.
Discusses how top AI engineers earn $250K+ by building systems around models rather than training them, with a breakdown of key skills like memory systems, harnesses, loop engineering, and tracing.
This tweet discusses the importance of asking clarifying questions in system design interviews, explaining how questions drive better architecture than rote diagrams.
The author shares lessons from building an agentic system at work, describing failures with a giant prompt, excessive tools, and dynamic sub-agents, and ultimately finding success with a fixed orchestrator and specialized child agents for each domain.
A technical blog post exploring the hidden complexity of job queues, discussing why they are deceptively tricky and offering useful lenses for system design such as being wary of queues, limits, and fault models.
A developer details Observation-Oriented Programming (OOP), a paradigm for organizing a swarm of terminal AI agents around watching observability data rather than task execution. The system uses tmux, cron, bash, and an append-only log file, with agents acting as observers that correlate signals and materialize actions only after interpretation.
This article argues that achieving exactly-once execution in distributed systems is impossible, and that agent stacks must be designed to deal with this limitation.
A Principal Engineer at Atlassian shares a completed 25-day Twitter thread series on system design scaling fundamentals, compiled into a single resource.