This site started as a personal collection of solutions, how-to notes, data, and technical information I pieced together while working through real problems. At first, it was just a notebook sitting on my desk, something I referenced when I needed to remember how I solved something.
As the notebook grew, so did I.
Over the years, I have learned a lot about technology, but I have also learned more about the people behind it. I started reaching out to writers, engineers, and builders whose work had helped me, simply because I wanted them to know that what they shared made a difference.
The responses surprised me. Many of them had no idea their work had helped someone else in such a meaningful way. They were not writing for attention or popularity. They were documenting what they knew, sharing what they loved, and contributing in their own quiet way.
That is what I want this site to be.
A place where I document what I learn, preserve solutions that took effort to figure out, and hopefully help someone else who is trying to solve a similar problem. I believe even small contributions can have a real effect. A single post, note, diagram, or command can save someone hours, unblock a project, or encourage them to keep going.
This site is my technical notebook, my lab record, and my way of giving something back.
What I write about
The work here centers on infrastructure: Linux, VMware, OpenStack, OVN and Open vSwitch, MikroTik, routing, overlays, public IP transit, storage, automation, and home-lab systems built to behave like small production environments.
Cited work
One of my MikroTik OSPF posts was cited as Reference [9] in an academic paper on multi-campus OSPF network design: Patricio et al., Revolutionizing Multi-Campus Communication: A Next-Generation OSPF-Based Network Design for NVSU’s Distributed Learning Environment, Journal of Computer Sciences and Applications, Vol. 14, Issue 1, pp. 1–7 (2026).
Elsewhere
Working with me
I’m currently open to paid work in tech — broad scope, from hands-on infrastructure and networking through senior engineering and leadership roles. Remote-first preference; hybrid in the New York area is a strong second; on-site in NY is also fine. The simplest way to reach me is a message via LinkedIn.
— Carmine