Writing about Agentic Engineering Patterns #
23rd February 2026
I’ve started a new project to collect and document ** Agentic Engineering Patterns**—coding practices and patterns to help get the best results out of this new era of coding agent development we find ourselves entering.
I’m using Agentic Engineering to refer to building software using coding agents—tools like Claude Code and OpenAI Codex, where the defining feature is that they can both generate and execute code—allowing them to test that code and iterate on it independently of turn-by-turn guidance from their human supervisor.
I think of vibe coding using its original definition of coding where you pay no attention to the code at all, which today is often associated with non-programmers using LLMs to write code.
Agentic Engineering represents the other end of the scale: professional software engineers using coding agents to improve and accelerate their work by amplifying their existing expertise.
There is so much to learn and explore about this new discipline! I’ve already published a lot under my ai-assisted-programming tag (345 posts and counting) but that’s been relatively unstructured. My new goal is to produce something that helps answer the question “how do I get good results out of this stuff” all in one place.
I’ll be developing and growing this project here on my blog as a series of chapter-shaped patterns, loosely inspired by the format popularized by Design Patterns: Elements of Reusable Object-Oriented Software back in 1994.
I published the first two chapters today:
talks about the central challenge of agentic engineering: the cost to churn out initial working code has dropped to almost nothing, how does that impact our existing intuitions about how we work, both individually and as a team?Writing code is cheap now - describes how test-first development helps agents write more succinct and reliable code with minimal extra prompting.Red/green TDD
I hope to add more chapters at a rate of 1-2 a week. I don’t really know when I’ll stop, there’s a lot to cover!
Written by me, not by an LLM
I have a strong personal policy of not publishing AI-generated writing under my own name. That policy will hold true for Agentic Engineering Patterns as well. I’ll be using LLMs for proofreading and fleshing out example code and all manner of other side-tasks, but the words you read here will be my own.
Chapters and Guides
Agentic Engineering Patterns isn’t exactly a book, but it’s kind of book-shaped. I’ll be publishing it on my site using a new shape of content I’m calling a guide. A guide is a collection of chapters, where each chapter is effectively a blog post with a less prominent date that’s designed to be updated over time, not frozen at the point of first publication.
Guides and chapters are my answer to the challenge of publishing “evergreen” content on a blog. I’ve been trying to find a way to do this for a while now. This feels like a format that might stick.
If you’re interested in the implementation you can find the code in the Guide, Chapter and ChapterChange models and the associated Django views, almost all of which was written by Claude Opus 4.6 running in Claude Code for web accessed via my iPhone.
More recent articles #
Conceptual integrity and counting lines of code- 19th August 2026Qwen 3.8 27B is excellent, but it defaults to wildly overthinking things- 16th August 2026Now we have a timeline of the OpenAI accidental attack against Hugging Face- 7th August 2026