Most cloud sustainability tools are built for sustainability officers. They pull three-month-old billing data, run it through a proprietary model, and produce a PDF that engineers never see. By the time you know your us-east-1 cluster emits twice as much as us-west-2 would have, it's been running for a quarter. The architecture is locked in. The carbon is already burnt. The only moment you can act
You asked Claude to build a feature. It worked. You shipped it. Six weeks later, you're adding something related, and nothing makes sense anymore. The code is technically correct but completely opaque. You can't remember why anything was structured this way. Claude can't figure it out either — it starts guessing, and the guesses start breaking things. This is the scenario I keep seeing. And it's n
I needed to coordinate background scripts running across different machines. The obvious answer was Redis. Everyone uses Redis for this. The tutorials all use Redis. The Stack Overflow answers all say "just use Redis." So I looked at what deploying Redis would actually cost me: A running Redis server I had to maintain A broker to connect workers to it Celery or RQ on top of that Memory-based stora