about

or rather, why this blog exists

I’m not really built to give presentations about myself.

and honestly, I only made this blog just to have some sort of showcase of what I work on at 2am when I can’t sleep and my brain won’t stop bothering me with thoughts and ideas about “the next cool thing I wanna try”.

I’m Nicola.
I work as a devops engineer, mostly because I find it so satisfying seeing stuff happening when I automate the hell out of an infrastructure.

most of the time, that means playing around with containers, pipelines, virtualization software and monitoring stacks.
the usual suspects of the devops world, nothing too fancy or new.

but whenever I’m not working at my full-time job, I’m experimenting with whatever I think could be interesting enough.

what does that mean? I don’t know either, but this blog will be the home of every intrusive thought (or rather, intrusive project) that I think is challenging and cool enough to actually be developed.

the only thing that will remain constant throughout every single project I make is my approach in how I design them.

I don’t just want to build a simple prototype, an mvp.
I want to build systems that are scalable, stable and secure.
systems I can trust, systems I can automate without the need to constantly check if they have succeeded or not.

here you will find a collection of selected projects and every kind of post regarding them.
from their “manifestos” to case studies, release notes, design notes, tutorials and so on.

some of them will be closed-source, some of them will be open-source.
feel free to send me an email or a message if you want a demo of the closed-source ones.

this blog is as much a lab as it is a diary, of someone who loves to stay up late and tinker with systems he designed, swearing as if the missing documentation isn’t also his fault.

welcome to my 2am brain dump.
I guess you’re not that different if you read all of this.