I build the tools
I wish I had.
I'm a tech nerd at heart. I started my journey as a generalist full-stack developer, but over time, I found my true calling in the depths of backend engineering—where milliseconds matter and scalability is the only currency.
Current Focus
NeuronArchive
I'm currently building Neuron, a secure remote code execution infrastructure. It handles untrusted code execution across multiple languages primarily for competitive programming platforms.
It's an engineering playground where I'm solving deep systems challenges—from architecting warm/cold container pools to optimizing kernel-level resource isolation. I'm currently in the third phase of optimization, pushing latency down to the bare minimum.
Founding Engineer @ Codolio
I served as a Founding Engineer at Codolio, where I manage the entire lifecycle of the platform. From designing the frontend and architecting the backend to handling deployments and building browser extensions, I own the stack end-to-end.
Node.js to Go: A Love Story
Node.js was my go-to for a long time. It was familiar, flexible, and got the job done, so I stuck with it.
At some point, I wanted to learn Go. And the best way I know to learn a language is simple — actually build things with it. So I started using Go for backend work.
Since then, Go slowly became my favorite. I liked how simple and predictable it felt, how easy concurrency was with goroutines, and how confident I felt shipping backend code.
Today, Go is my primary backend language — not because Node was bad, but because Go just felt right.
Why buy when you can build?
I don't just build tutorial apps. I build the stuffs I need for my own digital existence. If I need a tool, my first instinct isn't to find a SaaS—it's to open my IDE.
Neuron
A distributed code execution platform. I engineered it to handle high concurrency safely, learning deep lessons about Docker internals and OS-level resource management along the way.
Formwix
A config-based form builder library. I wanted a way to generate complex, dynamic forms from simple JSON configurations, so I built a library to handle state, validation, and rendering automatically.
Personal OAuth Provider
Why rely on simplistic auth libraries? I implemented my own OAuth2 provider to truly understand the flow of tokens, sessions, and security protocols.
Custom Analytics Logger
I wanted to know who visits my site without handing data to Google. So I built a high-throughput logging service (using Supabase) tailored exactly to my metrics.
Let's Connect
I'm always engineering something new. If you want to chat about distributed systems, Go, or just geek out over tech, feel free to reach out.