Posts

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. ...

The memory problem Claude Code has a problem: it forgets everything. Close the session, open another one, and it’s like talking to someone who doesn’t know you. You can load context with CLAUDE.md, sure, but what about half-finished tasks? Bugs you found but didn’t fix? The plan you had for tomorrow? There are three complementary solutions: Linear (or your product tool), Beads (git-backed plugin) and Tasks (integrated in Claude Code). Each one for a different time horizon. ...

The infinite context problem Imagine you ask Claude to investigate how authentication works in your project. It starts reading files. Lots of files. Suddenly you have 50,000 tokens of context filled with code you only needed to consult, not remember. Now every response is slower. And more expensive. And when you want to do something else, all that context is still there, taking up mental space. The solution: subagents. You launch a specialized agent that does the dirty work in its own isolated context, returns a summary, and disappears. Your main conversation stays clean. ...

The awakening of slowness You’ve been working on your data science project for a while. You have twenty notebooks, a few images, and the typical folder structure that seemed like a good idea three months ago. You run git status to see what you’ve changed and… you wait. And wait. And while you wait, you have time to wonder if the computer froze or if it’s just contemplating life. Spoiler: it’s not contemplating. It’s suffering. ...

The problem: teaching what you haven’t taught yet I have a programming course with 47 classes. Each class has notes (where I explain concepts) and labs (where students practice). And I have a problem: sometimes I use concepts in labs that I haven’t explained in the notes yet. “Okay, in this exercise use map to transform the list.” The problem? I don’t explain what the hell map is until three classes later. ...

The news nobody saw coming Last week, while you and I were peacefully struggling with node_modules, Anthropic dropped a bomb: they bought Bun. Yes, the company behind Claude decided their future involves a JavaScript runtime written in Zig by a guy who thought “what if Node, but fast?” Claude Code just hit a billion dollars in revenue, and apparently the first thing you do when you have cash to spare is buy development tools. ...

The Problem of Repetition Ever had to explain the same thing to someone twenty times? Now imagine that, but with a robot that also loses its memory every few hours. “No, Claude, the commit needs to pass tests first.” “Claude, I already told you to use the type: description format.” “Stop adding emojis!” This was my daily routine until I discovered Skills. These are instructions you write once and Claude follows forever. Like training a dog, but without the treats. ...

When robots forget Imagine hiring a brilliant programmer. They solve complex problems, write clean code, understand your architecture. But they have one tiny flaw: every few hours, their memory gets wiped. They start from scratch. They don’t remember what they were working on, what you decided together, or why the code is structured the way it is. That’s exactly what happens with Claude Code and other AI agents. When context fills up (and it fills up fast if you’re working on a real project), the system performs “compaction.” It summarizes the conversation and throws away everything else. The problem is that summary loses nuance, decisions, and most importantly, the state of ongoing tasks. ...