My journey began with a love for mathematics: the elegance, the logic, the puzzles. I discovered Machine Learning and saw it as the most beautiful application of math, a vivid intersection of probability, linear algebra, calculus, and code.

Despite my passion, getting into data science wasn't easy. The competition was stiff, and the entry barriers high. So I pivoted to web development, a more accessible path that would end up reshaping my career.

That pivot launched me into the world of JavaScript. I've worked extensively with React, Next.js, React Native, Node, and Express. I've built everything from frontends to APIs to real-time systems. It turned me into a builder.

But my love for systems and math never faded. As I ventured into DevOps, managing deployments, backups, observability, and monitoring, I began to see the internet for what it truly is: a collection of elegant, orchestrated Linux processes.

This deeper exploration rekindled my original fascination. Networking felt like math again: packets, routing, sockets, layers. Subtle yet immensely powerful. The internet, beneath the surface, is a masterpiece of engineering.

Though I moved away from formal ML roles, the mathematical thinking I honed there persists. It feeds into how I model systems, understand observability metrics, debug infrastructure problems and make critical decisions.

From frontend to backend to infra, I've gained a 360-degree view of how things work. I've handled production issues, optimized systems, configured load balancers, and studied open-source infrastructure to understand the 'why' behind the tools.

My experience across different teams, especially in DevOps and backend, has shaped my thinking. Understanding infrastructure isn't just about uptime. It's about performance, security, resilience, and clarity.

Everything clicked when I realized it's all just a system: the frontend, the backend, the protocols, the infrastructure, each a part of one grand machine. My engineering mindset evolved from writing code to understanding how everything interrelates.

I'm obsessed with the infrastructure layer: self-hosted systems, containers, failovers, cloud-native architecture, and observability. But I still build apps and write code. I just see the full picture now.

In my current role I am building a chatbot on an OpenRouter backend, and my job is to optimize it. Somewhere along the way this turned into my obsession: agents, AI, LLMs. Every new model that ships, every new agent that launches, I find a way to test it. Right now I am deep into fine-tuning, token optimization, and RAG pipelines, and honestly it is amazing. I started my journey with development, but I am getting closer and closer to the world I actually like.

There is a side track too. I am studying a little quantum programming and a little game development, the two topics I have never touched. I have a slight idea of blockchain: I started working with it and did not find it very sophisticated, though maybe I have not looked deep enough. Even so I find it interesting. Definitely interesting. After math, the one thing I have always really liked is physics. I have studied relativity and followed new developments in science for years, and quantum physics is what I keep reading about as an avid reader: what is going on in the quantum world, from the labs in San Francisco to wherever the field is heading. I will admit I have not done very well at quantum programming itself. AI and LLMs take most of my time, between trying new agents and creating content.

That content goes on my tech channel, littlebittech, where I post about the AI models and agents I test.

What excites me most is not choosing a niche, but seeing how it all connects. I find joy in solving real problems, whether through code, architecture, or understanding how a system behaves under stress.

I want to work in roles that embrace this holistic view, where I can connect the dots between frontend polish, backend logic, and infrastructure resilience. My goal is simple: build meaningful things while staying deeply curious.