I Build Because I'm Curious
Every project I've shipped started as a question: "What if I could...?"
- What if inventory management didn't require spreadsheets? → InvGenie
- What if I could chat with my PDFs? → PDF Sidekick
- What if I could automate Instagram posting? → InstaPoster
- What if an AI could write code for me in the browser? → Forge
Solving Problems, Not Chasing Trends
I don't build projects to add them to a portfolio. I build because I encounter a problem — either in my own work or in someone else's — and I have the tools to solve it.
This means my projects span a wide range:
- SaaS platforms for businesses
- Automation tools for repetitive workflows
- Creative tools for visual and audio expression
- AI agents for research and development
Learning by Building
The best way to learn something new is to ship a project with it. Every technology I've picked up — from Next.js to Web Audio API to Three.js — was learned by building something real.
The Builder's Mindset
You don't need permission to build. You don't need a perfect plan. You need curiosity, tools, and the willingness to ship imperfect things that solve real problems.