The story behind
the code

SINC NOVATION Group hired me as an apprentice. I didn't know what a REST API was. I did know I wasn't leaving until I did.

Those early months were humbling. Every line of code felt like solving a puzzle where someone kept changing the pieces. But something clicked — the moment I understood that coding wasn't about memorizing syntax, it was about learning how to think in systems.

I spent nights reading documentation, weekends building small projects that nobody would ever see. Not because I had to, but because I couldn't stop.

Three years later, I was architecting data pipelines and debugging at 11pm not because I had to — but because I actually wanted to know why it was breaking.

This is when I learned that good code isn't clever code. It's code that works when you're not there to explain it. It's infrastructure that doesn't wake you up at 3am. It's APIs that developers actually enjoy using.

I started treating every project like it mattered, because it did. Not just to the business, but to the craft itself. Every function was an opportunity to do it right.

Oracom GmbH. AI products. Automation at scale. The work got more complex. The curiosity got deeper.

Now I'm building systems that process millions of data points, architecting solutions that need to be both intelligent and reliable. The stack evolved — JavaScript, Node.js, Python, AWS, PostgreSQL — but the philosophy stayed the same: build things that work, build them well, and never stop learning.

Still here. Still shipping. Still finding new problems worth solving at 2am.