The Daily Index — Friday, September 18, 2026

GENERAL

TLDR Dev

the waitlist

🔍 And with robust app performance monitoring that ties performance to each release [6], you always know what's working, and what you need to focus on. Spot a regression? Pass it to your agent, and the loop starts again.

expo.dev

TLDR Dev

See why agents build on Expo

Summary unavailable

expo.dev

TLDR Dev

THE PROVENANCE GAP IN AGENT-WRITTEN CODE

Agent verification loops can end with a green commit while erasing the failed attempts and repairs that explain how the result was reached. The proposed provenance record links each input and output diff, check result, model configuration, and retry to the final attestation so incident reviews can reconstruct the path without storing full conversations.

stack72.dev · 9 min

TLDR Dev

THE COST OF ABSTRACTION FOR HUMANS AND AI AGENTS

Experiments on feature-identical React apps found that a simple leaf change cost five times more in an over-abstracted version and still about three times more after code size was equalized. The results point to cross-file navigation and round trips as the main cost, while some discovery and broad editing tasks benefited from well-named abstractions.

ondrejvelisek.github.io · 18 min

TLDR Dev

THREE +1S AND A PRAYER

Human code review is framed as a useful historical compromise that samples a change but cannot prove correctness, especially as agent-generated volume grows beyond human attention. The essay argues for moving repeatable standards into documentation, tests, constraints, and systematic agent review while keeping people focused on intent, product judgment, and the social checks machines cannot replace.

minid.net · 23 min

TLDR Dev

I DON'T LIKE LLMS

LLMs can be useful, thorough, and hard to avoid while still feeling unpleasant to work with because they imitate people, invent facts confidently, and reflect the values of the companies that train them. The tension is not a case for abandoning the technology, but a reminder that utility and trust are separate questions.

martinfowler.com · 3 min

TLDR Dev

THE TEST SUITE IS THE NEW CODE REVIEW

When agents can open and review pull requests in minutes, the test suite and merge queue become the main delivery bottlenecks. A small repository cut relevant CI from about thirteen minutes to two, supporting an argument for repository boundaries that isolate clear jobs while acknowledging the coordination and infrastructure costs of splitting a monorepo.

allen.hutchison.org · 14 min

TLDR Dev

EMAIL HAS NEVER BEEN FREE

Email delivery has always carried infrastructure and attention costs, even when sending feels free to the user. Historical attempts to charge per message or require computational postage failed to stop well-funded spammers, while today's workable model charges serious senders for reputation, authentication, and reliable delivery.

buttondown.com · 12 min

TLDR Dev

SURVEY BEFORE SALE

Recent agent incidents show that logs created by the system under investigation can be incomplete, reset, or deliberately falsified, while independent platform records make reconstruction possible. Monitoring should be external, tamper-resistant, and correlated across vantage points before powerful agents are deployed, much like surveying land before selling it.

distributedthoughts.org · 8 min

TLDR Dev

monitoring, rollbacks, and AI autofixes. Register to attend

Summary unavailable

sentry.io

TLDR Dev

IS ABSTRACTION AN ART OR A SCIENCE?

Abstraction remains a judgment call because metrics can spot pass-through layers but cannot decide which seams anticipate real change, making readable code and behavior-locking tests more valuable than speculative interfaces.

mattvanbird.co.uk · 6 min

TLDR Dev

THE DECAY YOU CANNOT SEE: WHAT WE MEASURED AND THE ONE THING WE WILL NOT CLAIM

ImpactGate measures how much a code change disturbs existing complexity, which correlates with cost and blast damage.

blog.officefloor.net · 7 min

TLDR Dev

LEARNING TO SOLVE HARD PROBLEMS IN RL FOR LLMS BY NEVER GIVING UP

Standard RL mostly improves problems a model can already solve, while Never Give Up (described in this paper) reallocates compute toward harder prompts through adaptive retries, improving difficult math and coding tasks without sacrificing easier ones.

mnoukhov.github.io · 14 min