On the Loop, Not In It — But Code Quality Still Matters

Yesterday one of my AI agents wasted 15 minutes chasing a bug that didn’t exist. The function was called transformPayload() — but it didn’t transform anything. It validated. The agent built three layers of transformation logic on top of it before realizing the name was a lie. I’ve seen this pattern dozens of times now. And it’s exactly why I think Kief Morris’s latest piece gets the big picture right but undersells one critical detail.

Technology Evolution Doesn’t Move in a Straight Line—It Spirals

The Proud Ops Colleague

Years ago, an Ops colleague proudly showed me something new. ClusterSSH—cssh [1]. A tool that opens multiple terminals to multiple machines—at the same time. You type once, it executes everywhere.

Back then, machines still had names. Ops folks knew their history, their specs, their quirks. They could tell you which server had been acting up last Thursday and what firmware it was running. And cssh? It let them follow the runbook consistently across every node. No more SSH-ing into machines one by one, hoping you didn’t forget a step on node 7.

Kiro Subagents: Scaling Development with Specialized AI Agents

When you’re building complex software, context management becomes your bottleneck. Your AI agent is juggling frontend components, backend APIs, database schemas, testing frameworks, and documentation—all competing for limited context window space. The result? Diluted focus and suboptimal outputs.

Kiro Subagents solve this architectural challenge by enabling parallel task execution through specialized, autonomous agents that maintain independent context windows.

🏗️ The Architecture: Parallel Contexts, Focused Execution

Subagents operate as independent processes with their own context management. This architectural pattern delivers several technical advantages:

🌅 The Dawn of the Renaissance Developer

It’s that time of the year. AWS Community gets ready for the event of the year: re:Invent. And Werner publishes his tech predictions [1]. Like every year, a densely packed piece with loads of gems in it. This year Werner came up with 5 major themes, if I didn’t miscount. I covered the first one in my initial post [2].

The second one is about:

𝗧𝗵𝗲 𝗔𝗜 𝗗𝗶𝘀𝗮𝗽𝗽𝗼𝗶𝗻𝘁𝗺𝗲𝗻𝘁 𝗚𝗮𝗽: 𝗔𝗿𝗲 𝗪𝗲 𝗠𝗲𝗮𝘀𝘂𝗿𝗶𝗻𝗴 𝗣𝗿𝗼𝗴𝗿𝗲𝘀𝘀 𝗼𝗿 𝗝𝘂𝘀𝘁 𝗖𝗵𝗮𝘀𝗶𝗻𝗴 𝗛𝗲𝗮𝗱𝗹𝗶𝗻𝗲𝘀?

There’s been incredible progress in #AI tools for software engineers—new agents, coding assistants, and integrated workflows are launching every week. Yet, when talking to customers, a common question keeps surfacing: are these AI investments really delivering value, or are they still more hype than help?

That’s why I found the latest Tech Lead Journal podcast with Laura Tacho (CTO at DX ) so insightful [1]. The episode dives into real-world research on AI adoption—and tackles the tough questions leaders are facing:   •  Why “acceptance rates” often mislead organizations   •  How to move past buzzwords and measure true AI impact (e.g. with DX’s practical AI Measurement Framework)   •  Which use cases save time today (surprisingly, stack trace analysis outranks code generation!)   •  Why AI should be treated as a strategic team extension, not a “magic bullet” or a replacement for developers.