I accidentally stumbled into building my own DevOps pipeline. I didn’t plan to do this, but the lab needs structure if it’s going to grow.
Here’s how it happened: I had a handful of experiments scattered around before this site existed. Then I started building the site while also starting new projects.
So there I was, migrating old projects and figuring out how new ones could all live together in harmony. That led to an overall site structure and project template. I went through a number of iterations, and the desire for consistency became a forcing function to think more carefully about how to organize things.
But suddenly I wasn’t just exploring questions. I was thinking about routing, subdomains, deploy rules, update logs… and that’s when I realized how much I don’t want to manage project pages.
I want to try something new, write a note about it, commit changes, and have everything mostly update on its own. Right now I’m doing the experiments and the ops work in parallel.
So I’m spending some time on infrastructure and DevOps (what I’m calling “Omorious Ops”) now, so that in the future I can spend more time exploring and less time on ops.