Pragmatic Engineering
The right solution isn't always the flashiest one. Think contextually.
Who I am, what I do and why I love this craft.
I'm a software engineer — but for me, writing code is only half the job; the other half is thinking about the system. How does it talk in the background, where does it break, how will I feel when I read this code three months from now — that's what actually interests me.
I work in the grey zone between backend and AI. My journey that started with .NET expanded into Python, TypeScript and LangGraph. RAG systems, agent architectures and event-driven backends sit at the centre of my interests — I try to build systems that ship, that scale, and that can tell you why they failed.
Outside of code: technical books, architecture diagrams on scrap paper, forgetting when I poured the third coffee, and occasionally playing the guitar.

The right solution isn't always the flashiest one. Think contextually.
Every project is an opportunity to explore a new domain.
User experience matters as much as developer experience.
Today's speed shouldn't become tomorrow's technical debt.
Building my personal site from scratch. A .NET 10 backend, Next.js 16 frontend, a RAG-powered assistant, and a sustainable architecture for content.