AI Native Dev

If an agent writes the code, who do you let merge it?

Some teams ship after a glance at the diff. Others want two reviewers. Same tools. @mreferre (@AWS) says the gap is trust, and only with trust can you build a factory that keeps agent costs in check.

tessl.io/blog/from-indi…

Loop engineering means designing the cycle an agent works inside, not the prompt that starts it. Lada Kesseler gives her agent one step at a time, makes it write the result to a file, then makes it read that file back and judge itself. She calls it a centrifuge. She also trusts AI-written tests less than AI-written code, and thinks most teams chasing a software factory are about to drown in garbage.

Watch the full episode at youtu.be/luf6zSOCKH4 or listen wherever you get your podcasts

Automating software development keeps moving the bottleneck: first it was code, then code review. LaunchDarkly CEO Edith Harbaugh argues the constraint now is the last mile, whether all that cheap code actually does anything for the people using it.

Watch the full episode at youtu.be/ao3GNietz1w or listen wherever you get your podcasts

Agents author 22% of merged PRs at the median company. Most still need a human chaperone, and there aren't enough to go around.

@arcolano : tessl.io/blog/there-are…

1,200+ agent PRs a week. About 75% merge without a human. 91% of review findings were real defects.

How @tessl_io got there: tessl.io/blog/75-of-tes…