Start small. Ship. Then grow.
MVP first. Add one feature at a time. Measure what’s used before optimizing anything.
How I Think
I don’t blame the user. I fix the tool.
Years in customer service. Training in psychology. A career shipping tools busy people use every day. Same habit: listen hard, design for real life, and don’t leave anyone stuck.
Where it started
Customer service is not a soft skill on my resume
Years of it taught me how to talk to stakeholders without jargon, pull the real need out of a messy request, and stay calm when something’s on fire. That muscle still runs every build I own.
- I hear what people need—not just what they asked for
- I translate between admins, advisors, engineers, and end users
- “No user left behind” means the tool has to work for the tired person on a phone, not only the power user
- I take projects when there’s time, space, and a net win for everyone involved
How I build
Safety and simplicity first. Clever second—if ever.
I design. Tools (including AI) write the boring parts. My job is keeping us on the right path: if a change drifts us off, we roll back to the last good version and try again.
Build in layers
Presentation, infrastructure, shared pieces. Each layer should stand alone so the next phase doesn’t force a rewrite.
Readable beats clever
Code is for humans first. Short functions. One job each. Human time costs more than CPU cycles.
Plan for failure
Things break. Logging, alerts, and clear ownership tell you where—before users do. Assume logs can leak; don’t put secrets in them.
Everything is a pipe
Input → transform → output. Reusable pieces. Freeze the predictable building blocks before stacking higher-level work on top.
Leave it cleaner
Boy Scout rule: every pass should make the system a little easier to debug than you found it.
Psychology
Data is about people. Even when it isn’t, it still hits them.
I studied psychology because I care how we decide and why we act. Once I started building software, that curiosity became a practical edge: design for bias, fatigue, and handoffs—not ideal users who read every label.
Don’t trust the pretty chart
Cognitive bias loves dashboards. I pressure-test the story the numbers want to tell—including my own.
Make it teachable
Plain language, chunking, clear cues. If only one person can run it, it isn’t done.
Edge cases are people
The new hire, the phone-only admin, the record the form forgot. Empathy isn’t a slogan—it’s a design constraint.
How I show up
Own it. Say the hard thing. Keep sharpening.
- I take initiative—and I own the outcome after launch
- Hard calls come with options and tradeoffs, not surprises
- I respond. No chasing required.
- Working versions get replaced when flexibility matters more
- Ideas are cheap. Shipping them is the scarce part.
- I often design, build, test, and launch alone—on a deadline
Some tools got rebuilt two or three times after they already worked—because “works” wasn’t flexible enough for the real job. That’s why the portfolio is full: I keep going until the tool fits the people who use it.