After years of building, shipping, and occasionally breaking things in production, I’m finally giving my writing a proper home. This site is where I want my technical notes to live: close to my work, easy to reference, and independent of any platform feed.
I spend most of my time thinking about how developers build with AI systems. That includes agent frameworks, SDK ergonomics, multi-agent workflows, cloud infrastructure, and the small API decisions that determine whether a tool feels obvious or awkward. A lot of that work is easier to understand through concrete examples than through abstract takes, so this blog will focus on what I have actually seen while building and maintaining developer tools.
Why Move Here?
I’ve been writing on Pure AI over on Substack, but I wanted full control: my own domain, my own design, and content that lives alongside my work rather than on someone else’s platform. So here we are: the blog now lives at evanm.me/blog.
Owning the site also makes the writing easier to connect to the rest of my professional context. If I write about agent framework design, it can sit next to the projects I am working on. If I write about engineering craft, it can connect back to the experience and systems work that shaped the opinion. If someone wants to follow up, the contact section is one click away.
That connection matters because technical writing is most useful when readers can evaluate the source. I am not trying to write generic commentary about where AI is going. I want to document the choices that come up when teams build tools for other developers: where abstractions help, where they hide too much, and where the boring operational details decide whether a design survives real use.
What to Expect
I plan to write about four main areas.
AI and developer tools. I will write about agent frameworks, orchestration, SDK surfaces, evaluation loops, and the difference between a demo that works once and a tool developers can build on repeatedly. I am especially interested in the places where product design and platform design meet: naming, defaults, error messages, debugging workflows, and the shape of APIs.
Engineering craft. Some posts will be about architecture decisions, debugging stories, and patterns that hold up after a system has real users. I like writing about the connective tissue: release discipline, observability, migration plans, and the tradeoffs that rarely fit in a launch post.
Working from Seoul. I am based in Seoul now, after earlier chapters in Redmond, New York, Shanghai, Buenos Aires, and Paris. That will occasionally show up here too. Building global software while living across different cities changes how you think about teams, time zones, language, and default assumptions.
Projects and experiments. I will also use this blog to explain side projects, research threads, and experiments that do not fit neatly into a resume bullet. Some will be polished. Some will be notes from the middle of figuring something out.
How I Want to Write
The format will stay practical. A good post here should leave you with a concrete idea, a clearer mental model, or a useful implementation detail. I will try to include the context behind decisions rather than only the final answer, because the context is usually where the lesson is.
I also want the site to become a durable archive. Social posts disappear quickly, and newsletters are hard to browse once they pile up. A small site with stable URLs is better for essays, reference notes, and posts that I may want to update as the tools change.
Let’s Go
If any of that sounds interesting, stay tuned. The best way to follow along is to check back here, read through the blog archive, or connect with me on LinkedIn.
I am starting with this welcome post because the intent matters. The site is not meant to be a content machine. It is a place for careful notes from someone actively building in the AI developer-tooling space, with enough surrounding context that readers and search engines can understand who wrote it, why it exists, and how it connects to the rest of my work.