<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>hi</title>
    <link>https://lyletagawa.com/</link>
    <description>Recent content on hi</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 02 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://lyletagawa.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Squirrel Threat Model</title>
      <link>https://lyletagawa.com/posts/squirrel-threat-model/</link>
      <pubDate>Sun, 02 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/squirrel-threat-model/</guid>
      <description>Squirrels have shut down Nasdaq trading twice. Beavers, cows, and sharks have taken down networks too, but misconfiguration, sabotage, and copper theft cause far more damage than any animal ever has.</description>
      <media:content url="https://lyletagawa.com/images/wan-failures.jpg" medium="image" />
    </item>
    
    <item>
      <title>Luck</title>
      <link>https://lyletagawa.com/posts/luck/</link>
      <pubDate>Sun, 26 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/luck/</guid>
      <description>Luck decides more than most are willing to admit. Hard work and grit determine how ready you are for it.</description>
      <media:content url="https://lyletagawa.com/images/luck.png" medium="image" />
    </item>
    
    <item>
      <title>Hyrum&#39;s Law</title>
      <link>https://lyletagawa.com/posts/hyrums-law/</link>
      <pubDate>Sun, 19 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/hyrums-law/</guid>
      <description>Hyrum&amp;rsquo;s Law says that with enough users, every observable behavior becomes a depended-upon feature. Your implementation details become your API contract, regardless of documentation or intent.</description>
      <media:content url="https://lyletagawa.com/images/hyrums-law.jpg" medium="image" />
    </item>
    
    <item>
      <title>Functioning As Designed</title>
      <link>https://lyletagawa.com/posts/functioning-as-designed/</link>
      <pubDate>Thu, 09 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/functioning-as-designed/</guid>
      <description>Traditional accident models assume every failure traces back to a broken part. STAMP treats safety as a control problem instead, which explains disasters where every component worked as designed.</description>
      <media:content url="https://lyletagawa.com/images/functioning-as-designed.jpg" medium="image" />
    </item>
    
    <item>
      <title>From Reno to BBR</title>
      <link>https://lyletagawa.com/posts/tcp-congestion-control/</link>
      <pubDate>Fri, 03 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/tcp-congestion-control/</guid>
      <description>In 1986, a network slowdown forced Van Jacobson to invent TCP congestion control. Reno, CUBIC, and BBR mark three different eras of solving that problem.</description>
      <media:content url="https://lyletagawa.com/images/tcp-congestion-control.png" medium="image" />
    </item>
    
    <item>
      <title>Bloom Filter</title>
      <link>https://lyletagawa.com/posts/bloom-filter/</link>
      <pubDate>Fri, 26 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/bloom-filter/</guid>
      <description>A Bloom filter checks whether something belongs to a set without storing the set. Firefox&amp;rsquo;s CRLite used one to compress revocation data for a billion certificates into 4 megabytes.</description>
      <media:content url="https://lyletagawa.com/images/bloom-filter.png" medium="image" />
    </item>
    
    <item>
      <title>Percentiles Don&#39;t Add Up</title>
      <link>https://lyletagawa.com/posts/t-digest/</link>
      <pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/t-digest/</guid>
      <description>Your p99 latency might not be a percentile. Averaging percentiles across replicas produces a meaningless number, and t-digest is the sketch algorithm that fixes it at scale.</description>
      <media:content url="https://lyletagawa.com/images/t-digest.png" medium="image" />
    </item>
    
    <item>
      <title>How LLMs Work</title>
      <link>https://lyletagawa.com/posts/how-llms-work/</link>
      <pubDate>Sun, 14 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/how-llms-work/</guid>
      <description>Working notes on how LLMs train and generate text. Probably mostly right, certainly incomplete.</description>
      <media:content url="https://lyletagawa.com/images/how-llms-work.jpg" medium="image" />
    </item>
    
    <item>
      <title>Goodhart&#39;s Law</title>
      <link>https://lyletagawa.com/posts/goodharts-law/</link>
      <pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/goodharts-law/</guid>
      <description>Goodhart&amp;rsquo;s Law says every metric used to track progress eventually gets used to fake progress instead.</description>
      <media:content url="https://lyletagawa.com/images/goodharts-law.png" medium="image" />
    </item>
    
    <item>
      <title>Distributed Causation</title>
      <link>https://lyletagawa.com/posts/distributed-causation/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/distributed-causation/</guid>
      <description>Distributed causation means complex failures have many causes spread across time, systems, and organizational boundaries. Fixing just one leaves the rest in place.</description>
      <media:content url="https://lyletagawa.com/images/distributed-causation.jpg" medium="image" />
    </item>
    
    <item>
      <title>Alignment Over Authority</title>
      <link>https://lyletagawa.com/posts/influence-by-alignment/</link>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/influence-by-alignment/</guid>
      <description>Alignment distributes decisions to whoever has the context. Authority centralizes them with whoever has the title, which is almost never the same person.</description>
      <media:content url="https://lyletagawa.com/images/influence-by-alignment.jpg" medium="image" />
    </item>
    
    <item>
      <title>Age-Based Live Event Caching</title>
      <link>https://lyletagawa.com/posts/live-event-caching/</link>
      <pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/live-event-caching/</guid>
      <description>LRU caching evicts the segments live viewers need when they rewind. Netflix&amp;rsquo;s patent US 12,621,504 B2 fixes this with segment age and distributed ownership, without bloating every edge server.</description>
      <media:content url="https://lyletagawa.com/images/live-event-caching.jpg" medium="image" />
    </item>
    
    <item>
      <title>LLM Context Biases</title>
      <link>https://lyletagawa.com/posts/llm-context-biases/</link>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/llm-context-biases/</guid>
      <description>Primacy bias, recency bias, sycophancy, and anchoring are predictable distortions in how LLMs weight information. Understanding them changes how you prompt, evaluate, and trust model outputs.</description>
      <media:content url="https://lyletagawa.com/images/llm-context-biases.jpg" medium="image" />
    </item>
    
    <item>
      <title>Jevons Paradox</title>
      <link>https://lyletagawa.com/posts/jevons-paradox/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/jevons-paradox/</guid>
      <description>Why efficiency improvements in technology often increase total consumption rather than reduce it, and how leaders can anticipate and manage the inevitable rebound.</description>
      <media:content url="https://lyletagawa.com/images/jevons-paradox-jam.jpg" medium="image" />
    </item>
    
    <item>
      <title>OODA Loop</title>
      <link>https://lyletagawa.com/posts/ooda-loop/</link>
      <pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/ooda-loop/</guid>
      <description>How John Boyd&amp;rsquo;s OODA Loop (Observe, Orient, Decide, Act) applies to technology leadership, and practical strategies for eliminating the bottlenecks that slow your competitive cycles.</description>
      <media:content url="https://lyletagawa.com/images/ooda-loop-f86.jpg" medium="image" />
    </item>
    
    <item>
      <title>Robust and Brittle... The Southwest Failure</title>
      <link>https://lyletagawa.com/posts/robust-and-brittle/</link>
      <pubDate>Sun, 08 Jan 2023 15:07:19 -0500</pubDate>
      
      <guid>https://lyletagawa.com/posts/robust-and-brittle/</guid>
      <description>Southwest Airlines has grown while desperately trying to be scrappy, creative and humorous. The challenge is that scrappy doesn’t scale well.</description>
    </item>
    
    <item>
      <title>PagerDuty Summit 2020</title>
      <link>https://lyletagawa.com/posts/pagerduty-summit-2020/</link>
      <pubDate>Thu, 24 Sep 2020 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/pagerduty-summit-2020/</guid>
      <description>Learn how you can move faster and focus on the things that matter by using incident analysis as your secret weapon. Operating at speed and at scale tests the capabilities of even the most experienced engineering teams. In this software world, it is inevitable that things will break. When they do, what do you do? Pick up the pieces and carry on? What if that’s not enough? Learning from incidents has taught us that broken things can lead to powerful opportunities, but only when we’re looking at them through the right lens.</description>
      <media:content url="https://assets.swoogo.com/uploads/medium/487256-5ea875614e45f.png" medium="image" />
    </item>
    
    <item>
      <title>Resilient Management</title>
      <link>https://lyletagawa.com/posts/resilient-management/</link>
      <pubDate>Mon, 17 Aug 2020 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/resilient-management/</guid>
      <description>Think about your team for a moment. How well is it functioning? Are you currently on a high-performing team, having found your groove and flow state as a group? Are you on a team that isn’t quite in that magical state of being yet, but it feels like you’re on your way? Are you feeling some friction—frustration, confusion—with your team? Or have you just joined a new team, so none of these apply yet?</description>
    </item>
    
    <item>
      <title>Manager README</title>
      <link>https://lyletagawa.com/posts/manager-readme/</link>
      <pubDate>Tue, 14 Jul 2020 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/manager-readme/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Chaos Engineering</title>
      <link>https://lyletagawa.com/posts/chaos-engineering/</link>
      <pubDate>Thu, 25 Jun 2020 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/chaos-engineering/</guid>
      <description>Chaos Engineering builds confidence in distributed systems by deliberately introducing failures before they occur on their own. The discipline shifts teams from reactive incident response to proactive resilience building.</description>
      <media:content url="https://lyletagawa.com/images/chaos-engineering.jpg" medium="image" />
    </item>
    
    <item>
      <title>Team Topologies</title>
      <link>https://lyletagawa.com/posts/team-topologies/</link>
      <pubDate>Thu, 14 May 2020 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/team-topologies/</guid>
      <description>Team Topologies provides four fundamental team types &amp;ndash; stream-aligned, platform, enabling, and complicated-subsystem &amp;ndash; and three core team interaction modes &amp;ndash; collaboration, X-as-a-Service, and facilitating. Together with awareness of Conway&amp;rsquo;s law, team cognitive load, and how to become a sensing organization, Team Topologies results in an effective and humanistic approach to building and running software systems.</description>
      <media:content url="https://images.squarespace-cdn.com/content/5b3296b78ab7229ecafcf4ed/1549553080029-RBNC0NOWOUE55VMFK8HB/main-logo-blue-text.png?format=1500w&amp;content-type=image%2Fpng" medium="image" />
    </item>
    
    <item>
      <title>Making Work Visible</title>
      <link>https://lyletagawa.com/posts/making-work-visible/</link>
      <pubDate>Fri, 08 Nov 2019 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/making-work-visible/</guid>
      <description>We grumble that there just aren’t enough hours in the day and that someone else sure seems to have a lot of free time. But we regular mortals only have twenty-four hours in a day. The problem is that we don’t protect our hours from being stolen. We allow thieves to steal time from us, day after day after day.  Who are these thieves of time?</description>
      <media:content url="https://itrevolution.com/wp-content/uploads/2017/03/MWV_3D_NEW-500x500.jpg" medium="image" />
    </item>
    
    <item>
      <title>Resilience</title>
      <link>https://lyletagawa.com/posts/resilience/</link>
      <pubDate>Wed, 30 Oct 2019 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/resilience/</guid>
      <description>Resilience Engineering is the framework for building systems that hold up when the unexpected is inevitable. Redundancy and rigorous testing still leave room for your system to fail anyway.</description>
      <media:content url="https://lyletagawa.com/images/resilience.jpg" medium="image" />
    </item>
    
    <item>
      <title>Remote-First vs Remote-Friendly</title>
      <link>https://lyletagawa.com/posts/remote-first/</link>
      <pubDate>Fri, 27 Sep 2019 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/remote-first/</guid>
      <description>So how do we do remote work right? It takes much more than the half-hearted “you’re allowed to work from home” policy you see at companies nowadays. Remote-first means working remote is the default. It means making sure your remote employees are as much a part of the team as those in the office.</description>
    </item>
    
    <item>
      <title>Turn the Ship Around!</title>
      <link>https://lyletagawa.com/posts/turn-the-ship-around/</link>
      <pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/turn-the-ship-around/</guid>
      <description>Concentrating decisions at the top discards the intelligence of people closest to the work. Marquet&amp;rsquo;s leader-leader model distributes authority to where information lives, producing organizations that outlast their leaders.</description>
      <media:content url="https://lyletagawa.com/images/influence-by-alignment.jpg" medium="image" />
    </item>
    
    <item>
      <title>The Dip</title>
      <link>https://lyletagawa.com/posts/the-dip/</link>
      <pubDate>Mon, 21 Jan 2019 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/the-dip/</guid>
      <description>How do you avoid killing something too early, or celebrating too early. And last, how do you know when to kill a dud?</description>
    </item>
    
    <item>
      <title>Just Culture</title>
      <link>https://lyletagawa.com/posts/just-culture/</link>
      <pubDate>Mon, 26 Sep 2016 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/just-culture/</guid>
      <description>A just culture balances the need for an open and honest reporting environment with the end of a quality learning environment and culture. While the organization has a duty and responsibility to employees (and ultimately to patients), all employees are held responsible for the quality of their choices. Just culture requires a change in focus from errors and outcomes to system design and management of the behavioral choices of all employees.</description>
    </item>
    
    <item>
      <title>Situation Behavior Impact feedback</title>
      <link>https://lyletagawa.com/posts/situation-behavior-impact/</link>
      <pubDate>Mon, 26 Sep 2016 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/posts/situation-behavior-impact/</guid>
      <description></description>
    </item>
    
    <item>
      <title>About</title>
      <link>https://lyletagawa.com/about/</link>
      <pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
      
      <guid>https://lyletagawa.com/about/</guid>
      <description></description>
    </item>
    
  </channel>
</rss>
