About me
Backend systems, automation, and architecture.
It started when a friend launched a business and needed help. I automated his workflow with a Discord bot — my first real build, written with ChatGPT when it was still new. That experiment turned into four years of learning and two years of shipping production software.
I enjoy building from scratch to understand how every piece fits. APIs, PostgreSQL schemas, automation pipelines, file storage, real-time systems — that's where I spend most of my time. When a project needs a frontend, I build it, but backend and systems work is what I care about most.
I also think a lot about system architecture: which database fits the workload, when to add caching, how to structure APIs so they stay maintainable years later. I'd rather ship something boring and reliable than something clever that breaks at 2 AM.
Reliability first
I build systems meant to run for years, not demos. Boring, tested, and maintainable beats clever every time.
Automation
If someone does it manually twice, it should be automated. That's where I started — and it's still what I enjoy most.
Architecture
Picking the right database, cache layer, and API shape for the workload — not defaulting to whatever's trending.
Frontend when needed
I handle frontend when a product needs it. My focus stays on the backend — APIs, databases, and the systems behind the UI.
How I work
Principles
Solve the real problem
A clever algorithm nobody uses is worthless. I start with what the user or operator actually needs — then build the simplest thing that works.
Understand the stack
Frameworks are tools, not religion. I build from scratch when it helps me understand the system — especially databases, APIs, and file storage.
Long-term thinking
Schema design, API contracts, and deployment choices matter more than shipping fast. I'd rather refactor early than debug production at midnight.
Get in touch
Ready to collaborate?
Available for freelance work and open to full-time roles. If you need someone to build backend systems, automation pipelines, or help with architecture decisions — let's talk.