ABWaters is a quiet place for writing about software, systems, craft, and the thoughtful practice of building things that last.

Most of what I write comes from years spent around real production systems, real delivery pressure, and the strange ways technical problems become people problems. I care about durable engineering, clear ownership, boring production, simple tools, and systems that do not require heroics to keep alive.

I am a software engineer by trade, so most of the writing here will probably orbit around software, engineering leadership, production systems, and the work around the work. But I will occasionally drift into other parts of my life: books, technology, amateur radio, family, local observations, tools, AI, and whatever else has been rattling around in my head long enough to become worth writing down.

Feel free to skip around and read the parts that interest you. This is not meant to be a tightly managed content strategy. It is a place to think out loud, carefully.

I try to be a systems thinker. That does not mean turning every subject into a diagram or pretending everything can be reduced to a model. It means trying to see the relationships, incentives, feedback loops, and consequences that are easy to miss when the complexity gets overwhelming. That habit has helped me make sense of software systems, organizations, and plenty of things outside of work.

I am also a husband, father, grandfather, obsessive reader, amateur radio operator, lifelong tinkerer, and lately, an AI enthusiast. I like understanding how things work, why they fail, and what we can learn when they do.

This site is intentionally minimal. No noise. No algorithm to feed. Just words, ideas, and the occasional strongly held opinion shared carefully.

Thoughtful disagreement is welcome. Comments are moderated because the goal is conversation, not a shouting match.

Thanks for stopping by.