Victor Freitas

I've been writing software professionally since 2016, and I've spent most of that time on the back end — APIs, the data stores behind them, and the containers and cloud plumbing that carry them to production. These days that means payments, where a bug isn't a rough user experience, it's somebody's money. The work I'm proudest of is a payment system that stayed boring under heavy load: no drama on the busiest days, which is the entire point.

It started with electronics. Long before I wrote a line of code I was the one taking things apart to see what made them work, and a computer science degree turned that curiosity into a career. I've just finished a postgraduate course in solutions architecture — the same itch at a wider angle. I still want to know what's happening one layer down; now I want to see how the whole thing fits together too.

That's why this site exists. When I finally get something running — an Elastic Stack that talks to itself, a container that behaves the same in production as it did on my machine — I write down what actually worked, including the parts the official docs skip. I'm not selling anything here. I just think these notes are more useful in the open than sitting in a file on my laptop. As a certain someone put it, "always pass on what you have learned."

Away from the keyboard you'll find me playing football with friends, working through more films and series than I can keep track of, or having a beer with people I like. My current rabbit hole is aquascaping — planted aquariums, which turn out to be a lot like software: you set up the conditions, wait, and then find out what the system actually wanted.