Blog.

Notes on software, design, and building products.

Stay grounded with your agent

Share on X

It's the fourth quarter of 2026, and building software has never looked more different. Today I want to reflect on some challenges as well as some key tips for having success managing robots and building high quality software. Now, I don't necessarily know if building software in 2026 is as fun as it was in 2019, but I do think there's a chance it just might be. There are some major trends in the industry right now around building software factories - emphasizing things like strict verification, e2e tests, and optimizing CI pipelines. In fact, the mandate for developers from industry leaders right now is that we should start focussing more on verification, and we can leave our days of sweating implementation details behind us.

This idea is obviously not a one size fits all. In my opinion, developers and teams need to talk before they run. Refining PR review bots, adding skills, scoped rule files, e2e tests, and robust verification checks are the bare minimum for teams that hope to start offloading verification and QA to the robots. It can be pretty daunting for developers and teams to embrace new tooling and new ways of working. But once these things are in place, we can start to truly shift the things that control our headspace throughout the day.

Another piece of this pie of course is the earlier portion of the SDLC. I'm not going to dive into requirement gathering and working with product teams here to figure out what to build, but these roles are changing rapidly too. As everyone from product managers to software developers is armed with incredibly smart intelligence, teams are better equipped than ever before to have the humans focus on the most important problems projects face, rather than fighting the applications and processes that we've been accustom to for decades. For developers like me, this means handling less "nit-picks" manually, worrying less about boilerplate code and syntax, and worrying less about scrutinizing every single line of code in my teammates PR.

With all of this amazing tooling, it can be easy to think at times that we may have just automated ourselves out of a living. However, that hasn't been my feeling in real life. That is, if you still want to feel in control of what you are shipping. It can be tempting to check-out all together, but that is also a quick fix - just like any other short-term drug is for relief or an escape. When you choose the short-cut, it might work for one PR, but the next thing you work on will be even harder because you'll need to re-learn where you are specifically at in building the system. So those quick short-cuts come back to bite you pretty quickly in real life I've found. In effect, agentic coding has its own dangerous temptations embedded in it, and it's up to the developer ultimately to give a damn, keep thinking critically, and to maintain a working and always evolving understanding of the system they are working on.

One approach I've found to help combat this dangerous cycle is to stay grounded with your agent. Ask you agents to walk through solutions in simple terms, ask them to explain concepts like you are a dummy until you understand things, and ask your agent every question that comes to mind. Rather then running a handful of skills in a loop and calling it a day, I've found the most success recently by reading tickets thoroughly myself first, before I send any messages to agents. Having a complete working understanding of the task at hand before beginning planning the solution with an agent is important. Walking through specific parts of implementations that you don't understand with your agent is also important. Although these things add time, they pay off in both the short and long term, because you'll be more prepared to ask good questions, build quickly with confidence, and react to problems diligently as they come up.

I think it's important right now to keep a consistent dialog with your agents. Ask questions frequently and check your understanding ritually as you work through plans and solutions.

Alright, time to go touch some grass. Thanks for reading!