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 →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 →If you use both Cursor and Claude Dev/Code, you’ve probably noticed they both want their own configuration folders (.cursor and .claude). Keeping your custom commands, rules, and skills in sync between them usually means a lot of copying and pasting. Here is a simple way to centralize everything in one .agents folder and use symlinks to keep both tools […]
Read More →I like Claude Code, but I don’t need it signing its name on every commit I make. By default, Claude Code appends a Co-Authored-By: Claude <noreply@anthropic.com> git trailer to every commit message. If you’ve never noticed it, run git log –format=”%b” | grep “Co-Authored” on any repo where you’ve used it. Go ahead. I’ll wait. Here’s what happens once […]
Read More →Every 2 years or so, for work or personal purposes, I invariably end up setting up a MacBook. As a developer, setting up my macOS for development is an exciting journey that enhances my productivity. I start by ensuring my system is up to date and then install essential tools like Homebrew, Node.js, and my […]
Read More →