The most underrated trick I have landed on is treating Claude Code as a coach for using Claude Code. The tooling already sees how you work: sessions, prompts, tools, and where time goes. The part most people skip is closing the loop: turn that signal into habits, not just a pretty chart. The workflow You can punt […]
Read More →Specs and change proposals live in the repo; Jira still owns Epics, Stories, and the board. You can do both without maintaining two truths: tie one OpenSpec change folder to one Story, leave tasks.md out of Sub-tasks, and link every ticket to openspec/changes/…. Most organizations will not retire Jira; this split is how you get SDD anyway without […]
Read More →“Most people are using MCP wrong,” said MCP’s co-creator, David Soria Parra. I agree. Because I made the same mistake. Engineers would do the obvious thing: wrap each REST endpoint as an MCP tool and shove them into a custom registry. The result? Zero value over just calling the APIs directly. Worse than zero, honestly. […]
Read More →“Keep It Simple” is old advice. It got interesting again the moment anyone could generate 500 lines of code in 30 seconds. KISS says systems and tasks should be as straightforward as possible. No unnecessary complexity. Fewer moving parts, fewer things to break, fewer things to hold in your head. It was good advice when […]
Read More →Claude Code can show a status line at the bottom of the terminal: a thin bar that updates as you work. It is easy to ignore until you start hitting context limits or wondering what a session actually cost. The bar keeps that kind of signal in peripheral vision so the main transcript stays focused on the […]
Read More →