I'm buying into this workflow more the more I use it, but the real gamechanger is (a) parallel threads in worktrees, with (b) enough lifecycle hooks to treat them similarly to spinning up a VM. Specifically for me that means that after I create a worktree I get some local config files copied over and Postgres duplicating my local dev and test databases so I can test in isolation, and then when I close out a worktree…
by far the most popular worktree manager