engineer
good software gets out of the way. it handles the edge cases, survives real users, and stays easy to change. i care about the parts nobody sees — the schema, the error paths, the quiet trade-offs — because that's what makes the surface feel effortless.
how i
work
three things i optimize for on every project, no matter the stack.
- clarity
- ownership
- follow-through
beginnings
i started the way a lot of developers start — by wondering how the things on my screen actually worked. the first scripts were small and mostly broken, but each one answered a question, and the questions kept getting better.
somewhere along the way, curiosity turned into a craft. i stopped just making things run and started caring about how they were built.
now
these days i build full-stack applications end to end — react and next.js up front, supabase and node behind it, shipped to production instead of living in a demo folder.
i co-authored a network-optimization paper presented at ieee nigercon 2026, and i've learned that the unglamorous work — validation, error states, audit trails — is usually the work that matters.
next
the goal is simple: keep taking on harder problems until the easy ones look different. internships first, then junior roles, and systems work that holds up at scale.
if it's worth building, it's worth building properly.
15+
Projects shipped
Production apps across web and mobile.
10+
Happy clients
Long-term partnerships and referrals.
2+
Years building
From MVPs to scalable platforms.
99%
Uptime focus
Reliability-first engineering mindset.
