I’m a backend engineer who became more curious about why systems behave the way they do in production than just how to build them. Early in my career, I focused on making things work. Over time, I started noticing something more interesting — Most problems don’t appear when you ship. They appear when systems grow. When data ages. When assumptions start breaking. That curiosity pushed me to think deeper about trade-offs, cost models, architecture decisions, and long-term consequences. I don’t claim to have all the answers. I’m not a “10x architect”. But I enjoy asking better questions: - What happens after 3 years? - What are we optimizing for? - What becomes expensive later? - What is hard to reverse? Through my content and conversations, I explore real-world backend decisions — especially around databases, scaling, and operational trade-offs. If you're a backend engineer trying to move beyond “it works” and develop stronger system-level judgment, I’m happy to think through problems together.