<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>LUMEN&amp;HOUSE — Thinking</title>
  <subtitle>Engineering essays on performance, type-safety, applied AI and product craft.</subtitle>
  <link href="https://lumenhouse.dev/feed.xml" rel="self"/>
  <link href="https://lumenhouse.dev/thinking/"/>
  <id>https://lumenhouse.dev/</id>
  <updated>2026-08-12T09:00:00+04:00</updated>
  <author><name>LUMEN&amp;HOUSE</name></author>
  <entry>
    <title>Edge Rendering, Honestly: What It&#x27;s Good For</title>
    <link href="https://lumenhouse.dev/thinking/edge-rendering-honestly"/>
    <id>https://lumenhouse.dev/thinking/edge-rendering-honestly</id>
    <updated>2026-08-12T09:00:00+04:00</updated>
    <summary>The edge is a latency tool, not a speed setting. What genuinely belongs there, what gets slower when you move it, and how to tell the difference.</summary>
    <author><name>LUMEN&amp;HOUSE</name></author>
  </entry>
  <entry>
    <title>In Defence of Boring Databases: Postgres First</title>
    <link href="https://lumenhouse.dev/thinking/in-defence-of-boring-databases"/>
    <id>https://lumenhouse.dev/thinking/in-defence-of-boring-databases</id>
    <updated>2026-08-12T09:00:00+04:00</updated>
    <summary>Why Postgres is almost always the right first answer, what it absorbs before you need anything else, and the honest cases for reaching elsewhere.</summary>
    <author><name>LUMEN&amp;HOUSE</name></author>
  </entry>
  <entry>
    <title>Performance Budgets That Actually Hold</title>
    <link href="https://lumenhouse.dev/thinking/performance-budgets-that-actually-hold"/>
    <id>https://lumenhouse.dev/thinking/performance-budgets-that-actually-hold</id>
    <updated>2026-08-12T09:00:00+04:00</updated>
    <summary>How LUMEN&amp;amp;HOUSE enforces performance budgets as a CI build gate, per route, so sites stay fast long after launch.</summary>
    <author><name>LUMEN&amp;HOUSE</name></author>
  </entry>
  <entry>
    <title>RAG Without the Hallucinations</title>
    <link href="https://lumenhouse.dev/thinking/rag-without-the-hallucinations"/>
    <id>https://lumenhouse.dev/thinking/rag-without-the-hallucinations</id>
    <updated>2026-08-12T09:00:00+04:00</updated>
    <summary>Most RAG failures are retrieval failures, not model failures. How we build grounded retrieval pipelines with evals, citations and a real refusal path.</summary>
    <author><name>LUMEN&amp;HOUSE</name></author>
  </entry>
  <entry>
    <title>Why We Ship React Server Components by Default</title>
    <link href="https://lumenhouse.dev/thinking/why-we-ship-server-components-by-default"/>
    <id>https://lumenhouse.dev/thinking/why-we-ship-server-components-by-default</id>
    <updated>2026-08-12T09:00:00+04:00</updated>
    <summary>React Server Components as the default and client interactivity as the opt-in: why the framework default decides what your codebase becomes.</summary>
    <author><name>LUMEN&amp;HOUSE</name></author>
  </entry>
  <entry>
    <title>Your Design System Is an npm Package</title>
    <link href="https://lumenhouse.dev/thinking/your-design-system-is-an-npm-package"/>
    <id>https://lumenhouse.dev/thinking/your-design-system-is-an-npm-package</id>
    <updated>2026-08-12T09:00:00+04:00</updated>
    <summary>Treating the UI as a versioned, semver-published dependency: why a design system only holds when it ships like software.</summary>
    <author><name>LUMEN&amp;HOUSE</name></author>
  </entry>
</feed>
