Development
Containers are VMs that share a kernel, your image is a whole operating system, and if you own the machine end-to-end, the second kernel is rent you don't owe.
In software, the generalist is your best engineer. The one who hedges in public, asks dumb questions, and somehow ships everything by Friday.
Twelve years on Nano because Vim fails my 3am-flu test. Micro is what I should have been using the whole time, and Ctrl+Q quits it.
SQL survived every replacement attempt not because it won, but because its challengers attacked the wrong layer.
I boilerplated too close to the sun and ended up with a new way to build web apps. And somehow it's not a framework.
I added a blog to my portfolio site. Astro got out of the way entirely. That's rarer than it sounds.
AWS has a free tier. It is weirder, more generous, and more dangerous than you think. Three years of building Lambda backends taught me how to make it sing.
After looking at SOPS, Parameter Store, Vault: Infisical might be the homelabber's best friend.
Homelabbing is genuinely fun. I want to say that upfront, before I tell you about the time I locked myself out of my own infrastructure for an afternoon.
"One container for the whole machine" is just a VM with extra steps. A week later: the steward container pattern. A thin Alpine image that orchestrates MORE containers. Don't extend scratch images. Use them.