About

I'm Mike. I write about software architecture the way I actually practice it — solo more often than not, with AI in the loop, and using methodologies (DDD, event storming, Jobs to Be Done) that were designed for rooms full of people I don't have.

Most of what shows up here started as a problem I was banging my head against on a Tuesday. If the writing reads a little raw, that's why. I publish thinking-in-progress because by the time it's polished I've usually lost the thread of what made it worth writing.

Who this is for

This blog is for you if…

• You've read enough Evans and Vernon to know DDD assumes a team, and you're trying to do it alone.
• You've integrated AI into your work and are quietly wondering which decisions you've stopped making.
• You like methodology but have given up on the workshop industrial complex.
• You suspect most architecture problems are vocabulary problems pretending to be technical ones.

I don't have a course to sell. I don't have a funnel. The newsletter, if you're into that, is one email per post — that's it.

Saying hi

If something here helps you, that's the whole point — and I'd love to hear about it. If something here is wrong, I want to hear about that even more. The best mail I get is from somebody disagreeing with a post from three months ago.

hello@coada.dev is the fastest way to reach me. I'm slow to reply but I read everything.

— Mike