Software engineer · Founder
Production systems, clear craft, long term thinking.
Go, Kubernetes, and distributed backends. From MVP to scale. Code as craft, not “just ship it.”
What you keep
Systems that work while you sleep.
01
Ship
Launch in weeks, not months.
A modern stack and deploys that do not wait on a ceremony.
02
Sleep
It stays up through the night.
Monitoring and a response path exist before the first user.
03
Scale
Ten times the traffic, same core.
The architecture absorbs growth instead of asking for a rewrite.
04
Cost
The bill stays honest.
Cache, queries, and right-sized machines. About forty percent less waste.
The stack
Tools I actually ship with.
Languages
Go
TypeScript
JavaScript
Frontend
Next.js
React
Tailwind CSS
Backend
Node.js
Bun
PostgreSQL
Redis
REST APIs
Backend
GraphQL
WebSocket
DevOps
Kubernetes
Docker
Terraform
CI/CD
Cloud
AWS
GCP
Tools
Git
Architecture
Microservices
Four movements
Idea, then a system that stays up.
Roadmap, architecture calls, and a timeline you can actually keep.
System designStackRisk
Writing
Thoughts & technical deep dives
After the launch
He built the payment path from nothing. We have moved millions since, and it has not gone down.
Deploys went from hours to minutes. He also left the team able to run it.
He argued with the product until it was the right one. We shipped in six weeks.
A short note is enough.
Tell me the system you need. I reply with a straight read on scope.