I'm a web and mobile developer based in Skopje, with over a decade of professional experience building real products. My journey started in 2014 when I wrote my first lines of PHP, not knowing it would grow into a full career across multiple languages, platforms, and problem domains.
In those early years, PHP was my entire world. I learned how servers think, how data flows, how a poorly written query can quietly kill a product at scale. Gradually, real client projects started pulling me in new directions. Python came next, then Ruby on Rails, then the JavaScript ecosystem with Node.js and React on the frontend side. Flutter arrived when mobile became impossible to ignore. Each language taught me something the previous one could not, and together they shaped how I approach problems today.
My original plan was simple: become a great frontend developer. I liked the idea of building things people could see and touch. But the projects that actually landed on my desk were never that clean. They needed someone who could wire up the API, design the data model, handle the deployment, and then build the interface on top of it. So I learned. I kept learning. And somewhere along the way I realized I had quietly become a full stack developer without making a conscious decision to do so.
If I am honest with myself, the backend is where I feel most at home. There is something deeply satisfying about well-designed architecture: a clean REST API, a Docker setup that behaves the same on every machine, a class hierarchy that makes the next developer's job easier instead of harder. I care about code that is readable, maintainable, and built to last longer than the deadline that produced it.
What I enjoy most is working on a project from the ground up. Requirements, architecture, implementation, deployment. The whole thing. Not because I want to do everything myself, but because understanding every layer makes each individual layer better. When I write a frontend component, I know exactly what the API behind it can and cannot do. When I design a database schema, I already have the business logic in mind. That end-to-end perspective is, I think, the most valuable thing I bring to a project.
More recently, AI and machine learning have become a serious part of how I work and what I build. I integrate large language models into products, design the backend infrastructure that makes AI features reliable at scale, and think carefully about where automation genuinely improves a user's experience versus where it just adds noise. Working with LLMs in production is a different kind of challenge than traditional software, and I find that challenge genuinely interesting.
Outside of work I keep a close eye on how the tools I use are evolving. The backend world moves fast, the AI space even faster, and standing still is not really an option. I enjoy that part too.
