What I build
Enterprise applications, approval workflows, APIs, data-heavy systems, internal platforms, and side projects that try to earn their existence.
I build enterprise software, internal tools, APIs, data workflows, and product experiments. The work matters more than decoration, so this page keeps it simple.
A straightforward profile page is enough. No gradient theater, no fake futurism.
Enterprise applications, approval workflows, APIs, data-heavy systems, internal platforms, and side projects that try to earn their existence.
Good structure is not academic decoration. It should survive deadlines, maintenance, and people touching the code six months later.
Clear naming, hard edges, useful abstractions, restrained UI, and software that feels composed instead of overdesigned.
The interesting work usually sits where enterprise rigor meets product taste.
Backends and frontends that stay understandable as the system grows, instead of collapsing into folklore and accidental complexity.
SQL-heavy workflows, ETL processes, service integrations, and the operational plumbing that keeps business systems alive.
Developer tools, iOS applications, and smaller products where implementation quality and interface quality both have to hold up.
The places that matter more than a bloated homepage.
Repositories, prototypes, technical notes, and unfinished things worth keeping.
Stack OverflowAnswers, habits, and fragments of how I approached problems over time.
LinkedInThe formal version, for people who prefer the official packaging.
X / TwitterFragments, opinions, and whatever survives the internal filter.