Battery

I have a menu bar app that needs to know a number. A percentage from 0 to 100. To get it, it calls a server every 30 seconds. Do the math: 30 seconds means 2 calls per minute, 120 per hour, 960 in an 8-hour workday. Almost a thousand HTTP requests per day to read a number that sometimes doesn’t change for 20 minutes. That’s not monitoring. That’s harassment. The real problem isn’t technical. It’s political. When you depend on an API you don’t control — that’s not public, that has no documented rate limits, that belongs to a company that can change their Terms of Service any given Tuesday — every unnecessary request is a risk. Not of timeout. Of getting cut off. ...

The crime scene Zaragoza, Hotel Pilar Plaza café. A latte, views of the basilica, and yours truly with a shiny new MacBook Air M3 ready to work a couple hours with Claude Code before a meeting. Two hours later: battery at 15%. Red alert. Panic. But how? I was just in a terminal writing code. No video, no Zoom, nothing that would justify this kind of consumption. I open Activity Monitor, Energy tab, and there’s the culprit: Ghostty, with an accumulated consumption of 3,600 over the last 12 hours. For context, Brave Browser consumed 125. Zoom with video, 99. Claude (desktop app), 46. ...