Posts

Running both personal and work projects on one dev machine, with commits going to different GitHub accounts. Don’t want to manually change user.email after every clone, and don’t want a global account-switching script. SSH key isolation + Git conditional config solves it once and for all. 1. Scenario Typical needs: Personal projects (~/personal/*) commit with personal GitHub account Work projects (~/work/*) commit with company GitHub account Each account has its own SSH key, no interference Identity switches automatically when entering different directories, no manual setup Additional pain points:

Half a year of running Claude Code, and the framing has shifted on me. Started out treating it like “VSCode + Cursor with a different vibe”; now it feels closer to managing a small team that can run jobs in parallel. This post is a sweep of the high-leverage features I actually depend on — hooks, MCP, subagents, worktrees, layered CLAUDE.md, when to /clear. Not a doc rewrite. The lens is “what a user with opinions actually does”, and you should be able to lift any block straight into your own setup.

CS146S — The Modern Software Developer↗ is a new Stanford course from Fall 2025, taught by Mihail Eric, with a heavyweight guest each week (Boris Cherny, Zach Lloyd, Isaac Evans, Tomas Reimers…). I worked through all eight weeks in the official assignments repo↗ and did the exercises along the way. This post is the consolidated note.

Origin story: spotted a Windows gist that wires Claude Code into system notifications↗ , written in PowerShell, useless on a Mac. Rewrote it for macOS, then added a Bark↗ channel — when a long job finishes and you’ve wandered off, the phone in your pocket should be the one that pings.