Why I write

I've been building software for more than fifteen years. I started as a kid who liked making things work, and that curiosity slowly turned into a career. I moved from freelancing in Serbia moving to Silicon Valley, where I joined small team building a cancer-screening platform. That period shaped me the most. It taught me ownership, reliability, and the value of building software that real people depend on.

I spent almost a decade in biotech after that. I helped start and grow teams at a few early-stage companies, including Karius, where we went from a tiny group to a real engineering org with real pressure, deadlines, and expectations. My work ranged from frontend architecture to distributed systems, and from building UI for clinical workflows to creating tools for scientists and lab staff. I learned how systems behave under pressure, how teams grow, how to keep quality steady when deadlines are tight, and how much communication matters when things get messy.

Today I work as a Team Lead in a Series B SaaS company. My work sits at the intersection of engineering leadership, AI strategy, systems design, and developer growth. I focus on bringing AI into real products, strengthening developer experience, and creating the conditions for teams to do their best work with clarity and consistency.

I write this blog to document what I'm learning. Not because I think I have it all figured out, but because writing keeps me honest. I care about practical engineering, thoughtful leadership, and teams that work well together. And if someone reads this and sees a bit of their own path in mine, that's enough.