<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Lit</title><link>https://lit.solar/blog/</link><description>Recent content in Blog on Lit</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 14 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://lit.solar/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>A Scandal in Modal</title><link>https://lit.solar/blog/2026-07-14-a-scandal-in-modal/</link><pubDate>Tue, 14 Jul 2026 00:00:00 +0000</pubDate><guid>https://lit.solar/blog/2026-07-14-a-scandal-in-modal/</guid><description>&lt;p&gt;&lt;img src="cover.jpg" alt="Silicon Valley Detective - The Engineer&amp;rsquo;s Deduction"&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I spent a full day dancing with Claude and chasing a test-suite hang that looked like memory pressure but turned out to be a microtask livelock in a hidden settings modal. The real culprit was a &lt;code&gt;useEffect&lt;/code&gt; that optimistically cleared a stale color theme, got rejected by a missing mock, reverted, and re-triggered itself - 44,570 times in 45 seconds - while every timeout starved silently on the macrotask queue. The biggest component in the app was innocent; the quietest one was guilty. A postmortem has all the technical details; and what follows is the same story retold as it deserved to be told.&lt;/p&gt;</description></item></channel></rss>