Logo maphew

Yak shaving worktrees

This morning I've been refining my git worktrees workflow / infrastructure.
yet more working on tools about tools instead of what I thought was going to be my main project.
yak shaving I believe they call it.
and yet, removing the paper cuts and friction sources is very important to getting work done.
sigh. anyway, what's been done:
 
On laptop ~/dev/beads - is the container for worktrees on Beads project
 

This is a git worktree setup each sub-dir is a worktree checked out to a branch

cd main
git worktree add ../new-feature -b new-feature
cd ../new-feature
# start hacking

Worktrees#

  • main: from steveyegge/beads. Sync frequently, don't change (always branch first)
  • fix-ci: debugging the persistent github CI problems
  • mui: monitor ui/webui experiments
  • worktree-test: dev on beads' incomplete worktree features

Metadata#

  • This file (readme.md)
  • _working_on/: {worktree}.md - the current area of focus. Ephemeral, move into history when done.
  • _history/: {worktree}/{worktree}_yyyy-mm-dd.md - where date is last-modified 
  • sync: script to backup the metadata files to Onedrive.

…

working on this has consumed 3 hours. I still don't know if it's been time well spent. I feel good about the mental model I've built up, and the general system feels ok. Though I do have some squishy feelings, for example everything else is solidly backed and controlled through git, but I'm using a home-grown DIY py script built with LLM for the metadata. That's less… solid, industrial.

Anyway, it seems to work. Time to get on with the main thing, which actually can't happen now because the physical meatspace life needs attending to for the next x hours. Ah well. I still feel more betterness than not.