About Me
A brief introduction
Hi there, my name is Duy /zwi/. I'm a software engineer who enjoy spent time architect solutions for my everyday "problems" by designing, building, constantly tinkering, and most of the time overengineering for the sake of it.
This is my corner of the internet where I learn in public, share what I discover, and document solutions to problems I probably didn’t need to solve in the first place.
The computing scientist’s main challenge is not to get confused by the complexities of his own making.
You can find my latest notes on the home page, or get in touch if you want to say hi.
Areas of interest
It all started with a small Kubernetes cluster that I built for homelab. It became the platform where I experiment with software and deal with the less glamorous, often hidden work of deploying and keeping applications running.“Full-stack” to me includes not only frontend and backend, but the whole system around them: how software is built, deployed, connected, stored, observed, secured, and delivered, along with the magic that keeps everything reliable.
While it is only for me, I try to follow cloud native best practices. The setup is only on-premise for now, but it will be able to extend to any cloud provider.
Most of the things I build start with an idea and some open source software. I like putting those pieces together into something useful and functional. The goal is usually to build the product I wish already existed.And sometimes, this means reinventing a perfectly serviceable SaaS wheel, because a weekend of engineering is apparently easier to justify than another subscription. Owning stuffs feels good. Maintaining it is the ongoing cost I prefer to forget.
I am particularly interested in improving personal LLM agentic workflows. By actively extending the tooling, surfacing relevant context, and assigning agents well scoped, independent units of work with clear interface contracts, I can get projects over the finish line considerably faster without sacrificing my understanding of the system or ownership of its solution architecture.
The best way to solve a problem is to explain it to someone (or something) else.