~/blog/series/infra
Infrastructure
From local dev to production-grade systems.
What this series is about
This series is short on purpose. Two posts, paired tightly. They cover the part of infrastructure I keep coming back to. Where does your stack actually live, and how much of it do you control when the vendor stops being friendly?
The first post is about getting more control over the server. Not in a nostalgia-for-the-2000s way. In the boring, concrete sense of being able to reach the machine that runs your software, change what is on it, and not be one billing dispute away from losing access. The second post extends that to your data. Same principle, different layer.
I am not arguing that everyone should self-host. Most of the time the trade-off goes the other way. But the trade-off only makes sense if you know what you are giving up, and the posts in this series are about being precise on that question. Where the line sits between convenience and dependence is yours to decide. The series exists so the decision is made deliberately.
Take back control of your data
GDPR is cracking, AI rules are loosening, and your data still runs on American servers. Time to take control yourself.
The meter was always going to switch on
GitHub Copilot went usage-based on June 1. Developers are angry. But the anger is pointed at the bill, not the thing that created it: two years of subsidised pricing that made an uneconomic habit feel like a productivity gain.