About
I find the real problem, then build the fix people actually enjoy using.
Who I am
I'm a problem solver by nature. I like building and fixing things that make people's lives easier. I love digging in until I understand how something works, and then finding the ways to make it faster, simpler or easier to use.
That has been true in production support, in full-stack work for clients, and in everything I build on my own time. Whatever it is, I'm thinking about the person who has to use it, and about what would make their day a little easier.
Built for the person the app forgot
I have ADHD, and it shapes how I build software more than anything else. Most people push through a boring extra step, a screen that expects them to remember something, or a number they have to work out in their head. I drop off. So I feel friction early, long before it shows up in a support ticket, and I design for someone tired, distracted and halfway out the door, because some days that's me.
It also gives me hyperfocus. When a problem grabs me, I follow it through every stored procedure and every repository until I understand all of it, and a mind that jumps sideways is how I notice that the bug in front of me is connected to something three systems away.
Pockets by Hoopy came from that. Every budgeting app I tried assumed I'd remember what my money was already promised to, so I built one that remembers for me and shows a single number, what's safe to spend right now. I build for people whose brains don't do what the app expects, because I know what it's like to be the person the app forgot.
I ask what the ticket didn't
Before I build anything, I want to know what the person is actually trying to do. A ticket once asked for "dashboards" and nothing else. When I asked the person who wrote it, she told me the ones she had made no sense and gave her nothing she could act on. So I built new ones around the decisions she actually had to make.
That question is also how I find the bigger problems. While building those dashboards, I noticed the history behind them was quietly wrong. People were showing up in roles they hadn't held yet, and nothing looked broken. The ticket would never have caught it. Most of the bugs worth fixing are like that, hiding behind a request that looks simple.
Before software, photography
For eight years I was a photographer, and my style was cinematic: hard light and deep shadow, borrowed from George Hurrell and the thousands of movies I've watched. The goal was to make people feel like the star of their own film. It trained the eye I still use: decide what the person on the other end should feel, then work backwards from that. It's why the things I build have to look good, not just be right.
I do the engineering. AI does the coding.
I design the system, the data model, the UX and the UI, then hand the implementation to coding agents and review what comes back. They're fast at the part that isn't thinking: writing the code, tracing a call through an unfamiliar codebase, reading a log.
The decisions stay mine: what the data has to be, which layer a fix belongs in, what's out of scope, and whether the result is actually right. Years of production debugging gave me a good nose for code that looks plausible and isn't.
The details are on Experience, and the things I've built are running on the desk.
Have something that needs building, or a role I'd fit?
michael@byhoopy.comBurlington, Vermont · LinkedIn