<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>System-Design on vnykmshr</title><link>https://blog.vnykmshr.com/writing/tags/system-design/</link><description>Recent content in System-Design on vnykmshr</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 30 Jan 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.vnykmshr.com/writing/tags/system-design/index.xml" rel="self" type="application/rss+xml"/><item><title>The first five minutes</title><link>https://blog.vnykmshr.com/writing/system-design-interviews/</link><pubDate>Mon, 30 Jan 2023 00:00:00 +0000</pubDate><guid>https://blog.vnykmshr.com/writing/system-design-interviews/</guid><description>&lt;p&gt;The prompt lands. A senior engineer, capable and prepared, starts drawing boxes. Load balancer, service tier, message broker, cache. Three minutes in, they are talking about shard counts.&lt;/p&gt;
&lt;p&gt;The design is not wrong. It is not a design either. It is a collection of patterns assembled against a problem that has not been defined.&lt;/p&gt;
&lt;p&gt;A system design prompt is deliberately loose. &amp;ldquo;Design a notification system for ten million users&amp;rdquo; has four different answers depending on what kind of notifications and which ones can be lost. &amp;ldquo;Design a URL shortener&amp;rdquo; has one shape at a thousand users and a different one at a billion. The looseness is the test. A person doing this work in production would not touch a whiteboard until the brief was tight enough to design against. The candidate who treats the interview as a different kind of activity from the work has missed what the interview is for.&lt;/p&gt;</description></item></channel></rss>