Menu

The Engineer Who Stopped Typing: How I Learned to Lead an Agentic Engineering Flow
📰

The Engineer Who Stopped Typing: How I Learned to Lead an Agentic Engineering Flow

DEV Community: microservices·Odumosu Matthew·about 3 hours ago
#gM3Wgic5
#devtomicroservices#devto#dev#agent#against
Long article (6576 words) — no AI summary yet.
Reading 0:00
15s threshold

A Field Guide to Agentic Engineering

By Matthew Odumosu, Senior Software Engineer

Part One: The Story

For most of my career, I was the one typing. I had late nights, branches with names I still remember, and the quiet pride of a bug fixed at 2 a.m. Writing code was how I proved I belonged in the room.

Before I ever led an agent, I worked as a prompt evaluator for Google. My job was to read model responses, compare them against written criteria, and decide which was better and why. I saw the same patterns over and over: answers that sounded confident and were wrong, answers that missed one instruction in a long request, answers that were right only by accident. That work taught me to read AI output the way a careful reviewer reads a pull request. It also taught me that the quality of the answer usually starts with the quality of the question.

So when AI coding agents arrived, I didn't welcome them. I watched them the way you'd watch a new hire who claims to know the codebase.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.