<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SystemDesign on NHE</title>
    <link>https://engholm.dev/tags/systemdesign/</link>
    <description>Recent content in SystemDesign on NHE</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>&lt;a href=&#34;https://creativecommons.org/licenses/by-nc/4.0/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CC BY-NC 4.0&lt;/a&gt;</copyright>
    <lastBuildDate>Sat, 11 Apr 2026 14:52:00 +0000</lastBuildDate>
    <atom:link href="https://engholm.dev/tags/systemdesign/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>🏀 What Basketball Taught Me About System Design</title>
      <link>https://engholm.dev/posts/system-design/</link>
      <pubDate>Sat, 11 Apr 2026 14:52:00 +0000</pubDate>
      <guid>https://engholm.dev/posts/system-design/</guid>
      <description>I’ve spent as much time on the court as I have in front of a terminal, and it’s striking how often the principles overlap. Whether you&amp;rsquo;re building a distributed system or coaching a team to the finals, the fundamentals of scale, latency, and reliability remain the same.&#xA;Here is why your tech stack is more like a basketball team than you think:&#xA;1. Throughput vs. Latency (The Fast Break) In system design, we talk about Latency (how long one request takes) and Throughput (how many requests we can handle at once).</description>
    </item>
  </channel>
</rss>
