Right now it seems to me the best way to work is with a bunch of Claude Code instances via Conductor. I m getting out north of 30 PRs a day this way, some of them very significant in scope. What this means, though, is a lot of context switching. I am not going to remember Continue reading "Running a dozen Next.js devservers without losing your mind"
You re working on a series of PRs, one per branch, each one based upon the precediung one. trunk -> my-feature-1 -> my-feature-2 -> my-feature-3 -> my-feature-4 Then you get a code review on my-feature-1 and you need to make a change. Now you need all the branches from my-feature-2 onwards to be rebased on the Continue reading "Rebase a whole stack at once"
In shadcn v3 there were two destructive vars in a theme, --destructive and --destructive-foreground. Various shadcn components used these the right way, but several used them wrong, using the background color (--destructive) for text. They mostly got away with this because both were generally a shade of red. But on dark backgrounds, it looked wrong. Continue reading "shadcn/ui v3/v4 and…
The normal behavior of atuin is to put either the command you matched onto your commandline, or nothing. So if you Ctrl-r and type something with no good match and exit, you lose what you have typed. You can Ctrl-g to get back what you had when you pressed Ctrl-r but anything you typed after Continue reading "How to keep your input and dismiss/cancel atuin"
#!/usr/bin/env zsh # Script to start monorepo development processes in separate terminals open_position_run() { local dir=$1 local cmd=$2 # Start the server osascript -e 'tell application "Terminal" do script "cd '"$dir"' & nvm use 20 & '"$cmd"' " in window 1 end tell' } open_position_run "/Users/bakert/monorepo/apps/app1 "pnpm dev" open_position_run "/Users/bakert/monorepo/apps/app2 "pnpm dev"