I was 11 years old. While other kids were collecting cards, I was collecting commands. My dad handed me a computer running Linux – not because it was easier, but because he wanted me to understand how things really work under the hood.
I discovered that with a keyboard and some logic, I could create worlds, solve problems, make a machine do exactly what I wanted. That feeling – that mix of power and curiosity – was the big bang of my professional universe.
The birth of a teacher
Here's the thing that shaped everything: I couldn't keep what I learned to myself. Every problem I solved, every configuration I figured out, every "aha!" moment – I wrote about it on my blog. Not for fame or money (I was 11!), but because I genuinely wanted to help the next person who'd face the same challenge.
That blog grew beyond my wildest expectations. People from around the world were finding my solutions, leaving comments, sharing their own discoveries. I realized something profound: knowledge shared multiplies, knowledge hoarded dies.
The long journey of learning
As I grew up, that passion led me through the expected path: Software Engineering degree, then a Master's in Artificial Intelligence. But here's what wasn't expected – I did both while working. First as a freelancer, building custom software solutions, then at a consulting firm tackling enterprise challenges.
Those early working years taught me something universities don't: how to listen to real problems, negotiate realistic timelines, and deliver solutions that actually work in the messy real world.
From builder to leader
Today, I work at a product company where I lead multiple engineering teams. I've built systems that serve millions of users, architected data warehouses with ClickHouse, led platform and operations teams, and assembled data engineering squads from the ground up.
I've given talks at conferences, taught classes at universities, run workshops for non-technical entrepreneurs looking to digitize their businesses. I maintain this blog, run a YouTube channel, and constantly share what I learn.
But somewhere along the way, I made a discovery that changed everything: watching someone on my team overcome a blocker and launch their project gave me more satisfaction than launching my own.
The real magic isn't in the code you write – it's in the confidence you give someone else to write theirs.
Why Pirobits exists
Pirobits is my answer to a question that haunts me: "What would I have needed 15 years ago to reach where I am today faster, with fewer mistakes, and more confidence?"
It's not just a blog or a community. It's the mentor I wish I'd had. A place where theory bows to practice, where AI is a tool for creation (not an end in itself), and where your business idea gets the technical guidance it needs to see daylight.
I've seen too many brilliant ideas die in notebooks while mediocre ones succeed simply because someone actually built them. I've watched talented people struggle with technical decisions that could have been shortcuts, not roadblocks.
My mission is simple: give you the knowledge, confidence, and tools so you can feel that same magic I felt at 11 – the magic of bringing your ideas to life.
What drives me today
Every day, I work with technologies that are just means to an end: React, Node.js, Python, Go, Docker, Kubernetes, ClickHouse, data pipelines, CI/CD, infrastructure as code – they're all just tools in the toolbox.
What excites me is using these tools to help people like you – whether you're a non-technical founder with a vision or a developer wanting to level up – turn ideas into products that people actually use and love.
Because at the end of the day, the best technology is the one that solves real problems for real people. And the best teacher is someone who's been in your shoes and wants to help you walk the path a little faster.
That's what I'm here for. That's what Pirobits is about.