The Wall Street Journal ran a piece yesterday on JustPaid, a 9-person Mountain View startup. They used OpenClaw and Claude Code to stand up seven AI agents that write code, review it, and run QA around the clock. In one month: 10 major features shipped. Each one would have taken a human engineer a month or more. This story is getting passed around as proof that the autonomous engineering team is h
MCP vs Skills: a practical decision guide for builders I need my agent to do X. Skill or MCP? If you build agents on Claude or anything MCP-compatible, this is the question that actually matters. The two patterns get pitched as alternatives. They are not. They solve different problems. Most production agents need both. Here is the decision rule, the framing for each, and the anti-patterns I keep
Last Tuesday I lost about three hours to a regression in our checkout service. The cart total was off by a cent on certain promo combinations, and the only signal was a Slack ping from finance with a screenshot. No stack trace. No exception. Just wrong numbers. I did what I always do first. I opened the diff for the last deploy, scrolled, squinted, and tried to feel my way to the bug. Forty minute
In March 2026, a rogue AI agent at Meta triggered a Sev 1 security incident. Sensitive company and user data was exposed to unauthorized employees for nearly two hours. The agent held valid credentials. It operated inside authorized boundaries. It passed every identity check. And yet. Identity and Access Management answers one question: Is this agent who it says it is? It doesn't answer: Was this
The Problem Nobody Talks About AI can write code, generate content, analyze data, design systems, and manage projects. It's getting better every month. The natural question: what's left for humans? The wrong answer: "AI will replace us." The right answer is uncomfortable: stop picking the best AI. Run multiple AIs in competition, and become the judge. Three rules, learned the hard way: Multiple
I Built a VS Code Extension to Bring IntelliJ’s “Show History for Selection” Experience If you come from IntelliJ, you probably miss one super useful feature in VS Code: Show history for selected lines. I built a new extension to solve exactly that. Show History for Selected Code This extension helps you inspect Git history for a specific code selection, not just the whole file. Shows commit h
Microsoft's 'Co-Authored-by Copilot' Tag: Unpacking the Strategic Play for AI Dominance in VS Code The persistent insertion of 'Co-Authored-by: Copilot' into commit messages within VS Code—often irrespective of GitHub Copilot's active contribution to specific changes—is far from a benign engineering detail. It represents a calculated, multi-faceted strategic maneuver by Microsoft, signaling a pr
I have a bad habit of jumping between projects. It's not a big deal. But it happens every single day. So I built rewind. rewind That's it. No setup, no IDE, no agent loop burning through tokens. Just one binary, one command, one LLM call. cargo install git-rewind GitHub: https://github.com/Chronos778/git-rewind Would love feedback — on the idea, the UX, anything. Still early days.