Mike Munoz

I’ve been building software for close to twenty years, and the part I still enjoy most is the moment a messy problem finally becomes simple. I like to sit with a problem until I really understand it, sketch it out, and then build the plainest thing that will hold up.

I also spent my first six years in the industry teaching calculus and mathematics at university. Explaining hard ideas simply, at a whiteboard or in a code review, is still a big part of how I work.

I care a lot about clean code. Not for its own sake, but because the next person to read it is usually a teammate, and often it’s me six months later. Good names, small pieces that do one thing, and tests that explain what the code is for.

Some of the work I’m proudest of is about people: helping a team find its rhythm, reviewing code with care, and making it safe to ask questions and own decisions. I’d rather leave a team stronger than leave behind a clever system only I understand.

These days I spend a lot of time on agentic coding, working out where AI genuinely helps a team ship better software and where it just adds noise.

Away from the keyboard you’ll usually find me scuba diving.