- The Town of Eagle DMR toolA Colorado town's federally enforceable water-quality reporting runs on a tool I rebuilt end to end, replacing an inherited system with no ingestion, no permit model, and, it turned out, wrong numbers.Town of Eagle, Colorado →
- Public water portalsThe public, not just water professionals, explores river conditions, monitoring data and annual results through portals branded for the agency that owns them.Upper Yampa · Keep It Clean · Cherry Creek · Middle Trinity →
Hello.
My name is Michael Barry.
I am a Full-Stack Engineer.
Scroll ↓
But I don’t write much code these days.
In fact, I haven’t written a traditional line of code in over a year.
My confession
AI writes my code.
There. I said it.
But let’s be real
Typing code was never the valuable part of software engineering.
So what exactly do I do?
Fair question.
The short version
I build systems that write it for me.
- 01Architect applications
- 02Define boundaries
- 03Create context
- 04Build reusable skills + agents
- 05Document decisions
- 06Establish acceptance criteria
- 07Design test + review loops
- 08Interrogate bad assumptions
Then…
I let machines type really, really fast.
ProblemArchitectureContextAgentsValidationSoftware
The reality is…
Software development is changing faster than it ever has before.
I’ve redesigned the way I work around that reality.
Not to write less software. To build more ambitious software.
Better. Faster. At a scale I couldn’t reach before.
But don’t worry
I didn’t delegate the part that makes me better.
Judgment, architecture, review, the occasional hard lesson. That part didn’t shrink. It became the whole job.
AI gives everyone a boat. I know how to swim.
Anyone can ship something that looks professional now. The profession starts when it breaks, when it scales, when it has to be right. You can’t generate that part.
5+ years. 50+ water resource clients. hundreds of production features. 22 operational workflow domains.
Scroll on. There is more.
Sec. 02 · The proof, in three parts
Production depth. Systems. Ownership.
- Headwaters: the platform monorepoI built the monorepo my team's application development runs on: fifteen production applications, eight shared packages, and three code generators, where provisioning a new authenticated client app is a command, not a project.LRE Water / Spheros Environmental →
- The capabilities-demo generatorNon-technical colleagues maintain a self-contained, portable capabilities demo (95 features, 38 client organizations) by editing an Excel workbook and running a generator.Internal portfolio infrastructure →
- CrossFit MF / Misfit Gym PortlandA Portland, Maine gym (est. 2009) gets a full marketing-site rebuild, specified up front in fourteen documents and executed autonomously against them.Built · launch anticipated September 2026Portland, ME gym →
- CommuniFitA passion project built out to a stable v1: a full neighborhood fitness platform with auth, a database, realtime notifications, transactional email, scheduled jobs and an admin suite.Fully functional · seeded data · never launchedPassion project →
Sec. 03 · Get in touch
Hiring for a senior product engineer who has figured out the AI workflow everyone claims to have?
Here is the other half of that question, which portfolios usually leave out: what I’m looking for.
A hard problem
Difficulty, not volume.
Ownership, end to end
An application, not a queue.
Autonomy, with a compass
Trust the how. Be clear on the why.
Room to grow
A ceiling above my head.
No contact form. Email works, and I answer it myself. You don’t have to be hiring to use it. If you’re somewhere in the middle of working out how a team does this without it going badly, that’s a conversation I want anyway.