Product truth over demo theatre
I label sample data, platform limits, and unfinished integrations plainly. Trust is a feature, including in portfolio work.
About / Business and technology
I care about the seams.
I work at the seams between business needs and implementation: where an operational problem becomes a requirement, a workflow becomes a system, and a technical decision affects the people using it.
My working definition
Analysis first, then a system people can evaluate.
My professional foundation is business analysis: clarifying needs, improving reporting, and translating operational requirements into practical systems. My independent software work extends that process into interfaces, domain rules, persistence, integrations, security boundaries, error states, and evidence that the journey works.
I am a U.S. citizen based in the United States, targeting U.S.-based and remote roles. I have built independent software projects since 2022 and am now concentrating that work into three deliberate builds: Immigration Helper, SPY Signal Desk, and Storefront HQ. They cover multilingual guidance, research decision support, and review-controlled commerce operations without being presented as formal software employment or finished products.
Principles
What I optimize for.
Logic that can stand alone
Rules engines, validation, permissions, and transformations should be testable without clicking through a browser.
Interfaces that explain the system
Good UX makes state, consequences, and recovery visible. Accessibility is part of that clarity—not a final pass.
Verification at the real boundaries
A passing unit test is useful; a persisted record, rejected unauthorized request, working production build, and clean browser console complete the argument.
Evidence, not adjectives
What I require before calling a build complete.
- A documented scope and explicit completion checklist
- Finished primary user journeys across mobile and desktop
- Verified persistence, server boundaries, and recovery states
- Focused tests for the highest-risk domain logic
- A passing production build with real browser verification
- Written limitations, trade-offs, and a reproducible review path
Current focus