How I approach the work
I like building software that feels useful from day one. That means I ask early questions about the users, the workflows, and the parts of the product that actually move the business forward.
On the frontend, I care about clear interfaces, responsive layouts, and pages that are easy to scan. On the backend, I focus on stable APIs, data models, authentication, integrations, and code that another developer can continue without friction.
I am usually the best fit for founders and small teams that want one technical partner who can take ownership, communicate clearly, and keep pushing the product toward launch.





