When you build a PowerShell project from multiple files, the natural structure is clear: enums first, then classes, then functions. Each group has its own place, and as long as dependencies only flow in one direction, that structure works perfectly. But sometimes a function depends on a class, and that class calls the function. There is no longer a clean boundary between the two groups — they need
The drift problem nobody told you about If you have used Claude Code, Cursor, Aider, or any other AI coding agent across more than two projects, you have felt this: You start project A. You copy the .agents/ folder (or CLAUDE.md, or .cursorrules) from your last project. You tweak two things. Done. You start project B six weeks later. You copy from project A. You tweak three things this time. Now
Cross-posted from the Stigmem blog. Today we're releasing stigmem v1.0: A stable, open-source specification and reference implementation for a federated knowledge fabric for AI agents. Stigmem = Stigmergy + Memory. Stigmergy (Greek stigma — mark; ergon — work) is the coordination mechanism you see in ant colonies and termite mounds: agents don't communicate directly with each other. Instead, they
The task at hand is drawing the circuit schematics for a robot I'm working on. I had already written down the components and the connections, all that's left is to draw it in KiCad. I had already started doing that, but then... I got sidetracked forcing Gemini to create the circuit using KiCad. I would have made progress if I had continued doing it by hand. I spent yesterday trying to generate an
More rules should mean better output. That's the intuition. I spent weeks building a comprehensive CLAUDE.md — 200 lines covering naming conventions, security rules, error handling, architectural patterns, import ordering, type safety requirements, and more. I was proud of it. I'd thought through every scenario. Then I scored the output. 79.0 / 100. My carefully crafted documentation was actively
Comments
I still remember the message. A developer on my team - sharp, careful - pinged me: "My Claude Code bill spiked $200 this week. Same workflow. Something's off." I had no answer. The built-in usage view showed session totals. The web billing page showed monthly aggregates. But neither could answer the only question that mattered: which specific turn ate the money? How do I improve the way I use Clau
This is part three of a series on display consistency in embedded systems. The first two parts were technical. This one is about why the technical parts worked. The picture: ATtiny85 thermometer. Neural network inference. QUAD7SHIFT display. Built from datasheets. He had datasheets. No Stack Overflow. No libraries to install. No AI to generate boilerplate. No tutorials that abstracted away the in