<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Lucent Codeworks</title>
	<link>https://lucentcodeworks.com</link>
	<description>Lucent Codeworks builds and repairs complex software for teams with hard problems — and leaves it clear enough for your own engineers to own.</description>
	<language>en-gb</language>
	<atom:link href="https://lucentcodeworks.com/rss.xml" rel="self" type="application/rss+xml" />
	<item>
		<title>Twelve questions to ask a development agency before you sign</title>
		<link>https://lucentcodeworks.com/writing/articles/what-to-ask-a-development-agency</link>
		<guid isPermaLink="true">https://lucentcodeworks.com/writing/articles/what-to-ask-a-development-agency</guid>
		<description>The questions that reveal how an agency actually operates - including the ones we would rather not be asked, and what a good answer sounds like.</description>
		<pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate>
		<category>hiring</category>
		<category>process</category>
		<category>agencies</category>
	</item>
	<item>
		<title>A technical due diligence checklist you can run yourself</title>
		<link>https://lucentcodeworks.com/writing/guides/technical-due-diligence-checklist</link>
		<guid isPermaLink="true">https://lucentcodeworks.com/writing/guides/technical-due-diligence-checklist</guid>
		<description>The questions we ask when assessing an unfamiliar codebase, in the order we ask them, with what each answer actually tells you.</description>
		<pubDate>Sun, 30 Aug 2026 00:00:00 GMT</pubDate>
		<category>due-diligence</category>
		<category>audit</category>
		<category>process</category>
	</item>
	<item>
		<title>The connection pool exhaustion that was not a connection pool problem</title>
		<link>https://lucentcodeworks.com/writing/technical/postgres-connection-pool-exhaustion</link>
		<guid isPermaLink="true">https://lucentcodeworks.com/writing/technical/postgres-connection-pool-exhaustion</guid>
		<description>A production incident where every symptom pointed at the database, and the actual cause was an HTTP client with no timeout three services away.</description>
		<pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
		<category>postgres</category>
		<category>debugging</category>
		<category>reliability</category>
		<category>node</category>
	</item>
</channel>
</rss>