<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Reading List</title>
    <link>https://reading-list.oddship.net</link>
    <description>A curated linklog of essays, posts, papers, and notes.</description>
    <atom:link href="https://reading-list.oddship.net/digests/rss.xml" rel="self" type="application/rss+xml" />
    <lastBuildDate>Mon, 24 Aug 2026 00:00:00 +0000</lastBuildDate>
    
      <item>
        <title>The hard parts are moving into the surrounding system</title>
        <link>https://reading-list.oddship.net/digests/2026-08-24-weekly-reading-2026-08-24/</link>
        <guid>https://reading-list.oddship.net/digests/2026-08-24-weekly-reading-2026-08-24/</guid>
        <pubDate>Mon, 24 Aug 2026 00:00:00 +0000</pubDate>
        <description>Intro
This week’s reading was less about one big model release and more about the systems around machine work. The strongest pieces kept pointing at the same shift: once generation gets cheaper, the scarce parts are maps, judgment, verification, durable storage, observability, and institutional accountability.
There was a second thread too. AI is making some hard work feel more reachable, but it is also making sloppy work scale faster. The useful distinction is not human versus machine. It is whether the surrounding system helps people understand, review, reset, and own what the machine produc…</description>
      </item>
    
      <item>
        <title>Agent work is becoming systems work</title>
        <link>https://reading-list.oddship.net/digests/2026-08-17-weekly-reading-2026-08-17/</link>
        <guid>https://reading-list.oddship.net/digests/2026-08-17-weekly-reading-2026-08-17/</guid>
        <pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate>
        <description>Intro
This week’s reading kept circling the same idea: agent work is becoming systems work. The interesting pieces were not only about smarter models. They were about harnesses, org context, verification loops, pricing, storage bugs, protocol choices, and the human habits needed when execution gets cheap.
The useful counterweight was also clear. Agents lower friction, but they do not remove judgment. The more work we hand to machines, the more the surrounding system has to make good work visible, reviewable, bounded, and recoverable.
Agent harnesses are turning into infrastructure
1) Organizat…</description>
      </item>
    
      <item>
        <title>Agent tools are becoming operating surfaces</title>
        <link>https://reading-list.oddship.net/digests/2026-08-10-weekly-reading-2026-08-10/</link>
        <guid>https://reading-list.oddship.net/digests/2026-08-10-weekly-reading-2026-08-10/</guid>
        <pubDate>Mon, 10 Aug 2026 00:00:00 +0000</pubDate>
        <description>Intro
This week’s reading had a clear through-line: agent tooling is leaving the toy-demo phase and turning into operating surfaces. The interesting pieces were about where agents run, what they are allowed to touch, how organizations expose context and write access, and what breaks when adoption is measured as a login instead of a craft.
There was also a useful counterweight to the agent-infra pile: several pieces argued that code, expertise, product judgment, and hobby craft are still real work. Better tools change the loop. They do not remove the need to understand the system or the people …</description>
      </item>
    
      <item>
        <title>Agent infrastructure is getting operational</title>
        <link>https://reading-list.oddship.net/digests/2026-08-03-weekly-reading-2026-08-03/</link>
        <guid>https://reading-list.oddship.net/digests/2026-08-03-weekly-reading-2026-08-03/</guid>
        <pubDate>Mon, 03 Aug 2026 00:00:00 +0000</pubDate>
        <description>Intro
This week’s reading was mostly about agents becoming less magical and more operational. The interesting work was in protocols, relays, sandboxes, session state, budget controls, model economics, document pipelines, and the unglamorous constraints that show up once agents touch real systems for long enough.
There was also a useful secondary theme: open and cheap models are becoming operationally important, but the gap between release headline and deployable reality is wide. The best pieces this week were the ones that read the docs, repos, specs, media, and operational guides instead of r…</description>
      </item>
    
      <item>
        <title>Verification is the bottleneck now</title>
        <link>https://reading-list.oddship.net/digests/2026-07-27-weekly-reading-2026-07-27/</link>
        <guid>https://reading-list.oddship.net/digests/2026-07-27-weekly-reading-2026-07-27/</guid>
        <pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate>
        <description>Intro
This week’s reading had a clear center of gravity: code generation is no longer the scarce part. The scarce parts are verification, judgment, context, identity, and the systems work needed to make agent-shaped workflows safe enough to use.
The good pieces were not anti-agent. Most of them assumed agents are useful and getting stronger. The sharper question was where to put human review, what kind of harness or workspace an agent should live inside, and which infrastructure assumptions break once agents produce code, credentials, logs, and security incidents at machine speed.
Software fac…</description>
      </item>
    
      <item>
        <title>When compute gets expensive, architecture gets interesting</title>
        <link>https://reading-list.oddship.net/digests/2026-07-20-weekly-reading-2026-07-20/</link>
        <guid>https://reading-list.oddship.net/digests/2026-07-20-weekly-reading-2026-07-20/</guid>
        <pubDate>Mon, 20 Jul 2026 00:00:00 +0000</pubDate>
        <description>Intro
This week’s reading kept circling the same idea from different directions: when raw scale is expensive, brittle, or politically awkward, the interesting work moves into architecture.
That showed up in AI coding workflows, where the useful question was not whether models can write code, but who owns the system’s ideas, interfaces, trust boundaries, and maintainability. It showed up in inference, where the story was less “use this model” and more “understand the workload, memory hierarchy, routing, batching, and serving control plane.” And it showed up in research and systems pieces where …</description>
      </item>
    
      <item>
        <title>When the harness gets boring, the market gets real</title>
        <link>https://reading-list.oddship.net/digests/2026-07-13-weekly-reading-2026-07-13/</link>
        <guid>https://reading-list.oddship.net/digests/2026-07-13-weekly-reading-2026-07-13/</guid>
        <pubDate>Mon, 13 Jul 2026 00:00:00 +0000</pubDate>
        <description>Intro
This week’s reading felt like a step away from agent demos and toward agent operations. The interesting posts were less about a model suddenly becoming magical, and more about harnesses becoming usable, runtimes getting more opinionated, and price-performance finally mattering in a way normal engineers can feel.
A second thread ran through the language and tooling discourse. The Bun rewrite fight, the TypeScript-in-Go framing, and the smaller Go&amp;amp;#x2F;toolchain side notes all pointed at the same question: what does engineering maturity look like once AI makes code generation cheaper but does n…</description>
      </item>
    
      <item>
        <title>Weekly reading: 2026-07-06</title>
        <link>https://reading-list.oddship.net/digests/weekly-reading-2026-07-06/</link>
        <guid>https://reading-list.oddship.net/digests/weekly-reading-2026-07-06/</guid>
        <pubDate>Mon, 06 Jul 2026 00:00:00 +0000</pubDate>
        <description>Intro
This week’s reading kept circling one practical question: what actually makes AI systems useful in the real world? Not just smarter models, but better ways to understand code, test interfaces, route traffic, manage costs, and shape the environments agents operate inside.
A second theme showed up underneath that one: a lot of the leverage is moving into interfaces and infrastructure. Several of this week’s links were really about the same shift from different angles, comprehension over generation, environment design over raw model capability, and operational realism over demo-friendly abs…</description>
      </item>
    
      <item>
        <title>Weekly reading: 2026-06-29</title>
        <link>https://reading-list.oddship.net/digests/weekly-reading-2026-06-29/</link>
        <guid>https://reading-list.oddship.net/digests/weekly-reading-2026-06-29/</guid>
        <pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate>
        <description>Intro
This week’s links felt unusually coherent. A lot of them circled the same underlying shift: the hard part of AI is moving out of the model and into the surrounding system, the loop, the permissions model, the eval layer, the cost controls, and the human operating model around all of it.
The best pieces also pushed on a second idea: good engineering is increasingly about making complexity survivable. That showed up in posts about agent harnesses, capability security, eval design, and even a beautiful essay on bounded cognition. If there’s a through-line here, it’s that the real leverage i…</description>
      </item>
    
      <item>
        <title>Weekly reading: 2026-06-22</title>
        <link>https://reading-list.oddship.net/digests/weekly-reading-2026-06-22/</link>
        <guid>https://reading-list.oddship.net/digests/weekly-reading-2026-06-22/</guid>
        <pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate>
        <description>Intro
This week’s reading kept pointing to the same conclusion: the center of gravity in AI is moving away from the model and into the surrounding system. The interesting leverage now lives in durable runtimes, tool and interface design, context management, orchestration loops, and the economics of when to use frontier, open, or local models.
A second theme was that open and local models are becoming operational questions, not just benchmark curiosities. The sharper discussions were about quantization, hardware tiers, distributed inference, and where “good enough” starts beating “best availabl…</description>
      </item>
    
      <item>
        <title>Weekly reading: 2026-06-15</title>
        <link>https://reading-list.oddship.net/digests/weekly-reading-2026-06-15/</link>
        <guid>https://reading-list.oddship.net/digests/weekly-reading-2026-06-15/</guid>
        <pubDate>Mon, 15 Jun 2026 00:00:00 +0000</pubDate>
        <description>Intro
This week’s reading converged on a useful correction to a lot of AI discourse: the hard part is less “having a powerful model” and more everything around it. The interesting work is in harnesses, loops, context, verification, permissions, deployment economics, and the organizational boundaries that decide what gets shipped.
A second thread was infrastructure becoming ideology. That showed up in arguments about engineering values, anti-vanity-metric critiques, export controls hitting model availability, open knowledge formats for agent-native wikis, and new payment&amp;amp;#x2F;authorization rails for…</description>
      </item>
    
      <item>
        <title>Weekly reading: 2026-06-08</title>
        <link>https://reading-list.oddship.net/digests/weekly-reading-2026-06-08/</link>
        <guid>https://reading-list.oddship.net/digests/weekly-reading-2026-06-08/</guid>
        <pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate>
        <description>Intro
This week’s saved reading clustered around a useful shift in emphasis: the interesting AI story is getting less about raw model capability and more about harnesses, feedback loops, operating discipline, and the shape of the org around the tools.
A second thread was that the market is starting to reveal what it actually believes. You can see that in enterprise spend caps, in production-infrastructure arguments, and in sharp critiques of product decisions when the experience does not match the hype.
Agent workflows, harnesses, and production shape
1) Dataroom and the case for local-first d…</description>
      </item>
    
      <item>
        <title>Weekly reading: 2026-06-01</title>
        <link>https://reading-list.oddship.net/digests/weekly-reading-2026-06-01/</link>
        <guid>https://reading-list.oddship.net/digests/weekly-reading-2026-06-01/</guid>
        <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
        <description>Intro
This was a thinner reading week, but the saved links still fit together surprisingly well. The strongest thread was about operating surfaces around AI: what makes coding agents actually useful inside an organization, and what happens when trust in an AI platform starts to fray.
There was also one good lighter link worth keeping in the mix, a reminder that not every useful reading roundup item has to be breaking news. Sometimes an old classic is still the right thing to resurface.
Agent infrastructure and shared operating context
1) Under the River
https:&amp;amp;#x2F;&amp;amp;#x2F;shopify.engineering&amp;amp;#x2F;under-the-ri…</description>
      </item>
    
      <item>
        <title>Weekly reading: 2026-05-25</title>
        <link>https://reading-list.oddship.net/digests/weekly-reading-2026-05-25/</link>
        <guid>https://reading-list.oddship.net/digests/weekly-reading-2026-05-25/</guid>
        <pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate>
        <description>Intro
This week’s saved reading had a pretty clean through-line: the interesting AI story is less about raw generation and more about workflow shape. Security teams are redesigning harnesses around stronger offensive models, infrastructure builders are questioning old cloud primitives, and protocol&amp;amp;#x2F;tooling work is slowly becoming more production-ready.
A second pattern: a lot of the most useful links were really about where judgment, verification, and operating constraints sit once agents get better. That showed up in security, org design, coding tools, and even protocol evolution.
AI security…</description>
      </item>
    
      <item>
        <title>Weekly reading: 2026-05-18</title>
        <link>https://reading-list.oddship.net/digests/weekly-reading-2026-05-18/</link>
        <guid>https://reading-list.oddship.net/digests/weekly-reading-2026-05-18/</guid>
        <pubDate>Mon, 18 May 2026 00:00:00 +0000</pubDate>
        <description>Intro
This week’s reading pile had a clear through-line: AI is getting better at speeding up execution, but the interesting work is shifting toward control surfaces, architecture, harnesses, review loops, org design, and security constraints.
A few of the strongest links made the same point from different angles. Coding agents are useful, but they need explicit structure. Stack choices are getting more reversible. And once generation gets cheap, curation, verification, and trust become more important than ever.
AI workflows, harnesses, and architectural control
1) I’m going back to writing cod…</description>
      </item>
    
      <item>
        <title>Agentic engineering grows up</title>
        <link>https://reading-list.oddship.net/digests/agentic-engineering-grows-up/</link>
        <guid>https://reading-list.oddship.net/digests/agentic-engineering-grows-up/</guid>
        <pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate>
        <description>Intro
I have been sitting on a large pile of AI links, tweets, papers, product launches, and side conversations for the last week or two. A lot of them looked unrelated at first: antirez writing about Redis Array, Anthropic shipping managed agents, Auth0 talking about auth for MCP, Mario Zechner pushing back on sparse-attention hype, Mitchell Hashimoto defending &amp;amp;quot;AI slop&amp;amp;quot; in a very specific context, Microsoft rebranding workflow redesign as frontier-firm strategy, and a small Indian civic-tech project making parliamentary reports searchable.
But taken together, I think they point at the same s…</description>
      </item>
    
      <item>
        <title>Things I read this week</title>
        <link>https://reading-list.oddship.net/digests/things-i-read-this-week/</link>
        <guid>https://reading-list.oddship.net/digests/things-i-read-this-week/</guid>
        <pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate>
        <description>Intro
I have been collecting a lot of links lately: blog posts, product launches, research notes, tweets, and side threads that felt worth saving.
So instead of forcing them into one big argument, I wanted to do a simpler weekly roundup: what I read, what stood out, and why each link felt worth keeping.
A few themes did repeat in the background, agent workflow design, review loops, tooling surfaces, and infrastructure, but I have tried to keep this mostly focused on the links themselves.
AI coding and workflow design
antirez on building Redis Array
https:&amp;amp;#x2F;&amp;amp;#x2F;antirez.com&amp;amp;#x2F;news&amp;amp;#x2F;164
Reading note: Mi…</description>
      </item>
    
  </channel>
</rss>
