It all started on a rainy morning, when the family computer froze for the third time in a row. Right then, somewhere between the restart and the smell of my mother’s fresh coffee, I realized I didn’t want to be a user anymore. I wanted to understand what was on the other side of that blinking cursor.
That’s what I’d say if this were an adventure novel or a biopic. The truth is a little less romantic: I was 16 and repeating my first year of high school — talented by nature, lazy by vocation. So I decided that either I hit the books, or I embraced a future of working under the blazing noon sun on a construction site. The computer was the most interesting distraction I had at hand, and that’s how I ended up falling in love with software.
I work with distributed systems, infrastructure as code, and the stubbornness to reject any abstraction I can’t explain to a colleague in three minutes. I believe every good software architecture is, above all, a good decision about what not to do. It took a lot of wrong decisions to conclude that less is more, and that the best line of code is the one you don’t write.
This paper is my portfolio — but it’s also a personal manifesto. In here you’ll find the projects I’m proud of, the articles I write when I have the time and the itch, and a classified ad asking you to get in touch, if this conversation makes sense to you too.
Enjoy the read.