software development

When I started Hamlogs, I didn’t sit down with a whiteboard and architect the perfect tech stack. I started building — then slowly replaced the parts that annoyed me. The result? A stack that’s fast, maintainable, and easy to self-host. And more importantly: one I actually enjoy working with. Here’s what’s under the hood of Hamlogs.com, and why I chose each piece. 🧱 The Core Stack NestJS gave me structure without slowing me down....

I didn’t intend to build another logbook. I set out to solve a problem I’d grown frustrated with. My amateur‑radio logging experience felt fragmented — desktop apps that didn’t sync, clunky tools, scattered QSL tracking. So, I quietly started building. No grand vision at first. Just a blank canvas and an evening of code. And today, just over three months later, Hamlogs.com goes live. ##The Why: A Signal in the Noise...