<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: ajpaulson</title><link>https://news.ycombinator.com/user?id=ajpaulson</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sun, 07 Jun 2026 20:38:55 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=ajpaulson" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by ajpaulson in "Harness engineering: Leveraging Codex in an agent-first world"]]></title><description><![CDATA[
<p>> The diagram below shows the rule: within each business domain (e.g. App Settings), code can only depend “forward” through a fixed set of layers (Types → Config → Repo → Service → Runtime → UI). Cross-cutting concerns (auth, connectors, telemetry, feature flags) enter through a single explicit interface: Providers. Anything else is disallowed and enforced mechanically.<p>Can anyone give me a simplified explanation of what they’re saying here? Having some trouble understanding.</p>
]]></description><pubDate>Sun, 07 Jun 2026 04:30:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=48431801</link><dc:creator>ajpaulson</dc:creator><comments>https://news.ycombinator.com/item?id=48431801</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48431801</guid></item><item><title><![CDATA[New comment by ajpaulson in "Rob Pike’s Rules of Programming (1989)"]]></title><description><![CDATA[
<p>I think I’m going to copy and paste this directly into my AGENTS.md file!</p>
]]></description><pubDate>Wed, 18 Mar 2026 13:44:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=47425744</link><dc:creator>ajpaulson</dc:creator><comments>https://news.ycombinator.com/item?id=47425744</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47425744</guid></item></channel></rss>