OVER DEZE AFLEVERING
➡️ Summary ➡️
A special crossover episode from the Revenue Engineer Podcast, hosted by Warren Walters — founder and chief programmer path planning officer (C3PO) of Cloud Code Academy, senior GTM systems engineer at Vercel, and a past AppsemblyLine guest. Warren flips the mic on Scott for a hands-on session about the workflow he uses at Tython building Permissions Assistant: pairing AI agents with git worktrees so the engineer stops being the bottleneck. Scott breaks down why git stash and cloned directories fall short, how worktrees create sibling working directories backed by one shared Git database, and how his bash scripts give every worktree its own isolated scratch org. Then it's demo time: three user stories for the weather proof-of-concept app from Warren's first episode — a five-day forecast, hardened error handling, and an account-page weather component — each built in parallel by its own Claude Code agent in its own worktree, then merged back into main by Claude itself, merge conflicts and all. Along the way Warren shares his own tricks, from the bang (!) command in Claude Code to treating every agent miss as a prompt to update your CLAUDE.md, and the pair field audience questions on GitLab support, org dependencies, and worktree sprawl.
➡️ Guest ➡️
Warren Walters https://www.linkedin.com/in/walters954/
Warren's Youtube Channel https://www.youtube.com/@Walters954
The Revenue Engineer Podcast https://www.youtube.com/playlist?list=PLxhxCFOxSp6iqVzzsNCdQBgnphxgXUX0m
Cloud Code Academy https://www.cloudcodeacademy.com
➡️ Takeaways ➡️
AI agents now write code faster than engineers can review it — the human is the bottleneck, and working one ticket at a time leaves that speed on the table
Git worktrees have been part of Git since 2015, but they're having a moment because they pair perfectly with agentic coding tools like Claude Code
git stash is a junk drawer — stashes get forgotten, and untracked or git-ignored tweaks make it clunkier still
Cloning the repo into a second folder creates two repositories with no knowledge of each other, and you pay for that convenience in merge conflicts later
A worktree is a sibling working directory backed by one shared Git database — and Git locks a branch checked out in a worktree so nothing steps on toes
Give every worktree its own scratch org: each sibling directory carries its own default org, so a deploy can never hit the wrong target
Bash scripts and npm commands automate the loop — create the worktree, spin up a scratch org, push metadata, assign perm sets, then tear it all down after merge
The workflow in action: three user stories, three worktrees, three Claude Code agents racing each other in parallel
Agent downtime is the new deployment wait — instead of reaching for your phone (or playing Tetris in MavensMate), pull down another ticket
A Claude instance in the main working directory can find the worktrees, merge every feature branch back into main, and resolve the merge conflicts itself
Warren's tip: the bang (!) prefix in Claude Code runs shell commands without leaving the session, and Claude keeps the context of what ran
When an agent gets something wrong, treat it as a trigger to update your CLAUDE.md steering files so it gets it right next time
Worktrees are a feature of Git itself, so they work the same whether your remote is GitHub, GitLab, or Bitbucket
The same pattern can work with sandboxes instead of scratch orgs — the teardown is just clunkier
Run through the whole workflow yourself with the weather-poc repo on Scott's GitHub
➡️ Youtube ➡️
Watch this episode on our Youtube channel
➡️ Keywords ➡️
git worktrees, AI agents, Claude Code, parallel development, scratch orgs, Salesforce ISV, Salesforce DX, agentic development, Warren Walters, Revenue Engineer Podcast, Cloud Code Academy, Tython, Permissions Assistant, DevOps automation, merge conflicts, feature branches, CLAUDE.md, weather POC, Vercel
➡️ Hashtags ➡️
#AppsemblyLine #Salesforce #ISV #ClaudeCode #GitWorktrees #AI #RevenueEngineer
Mentioned in this episode:
Simplify Your Salesforce Security Review
Get clear explanations, actionable insights, and step-by-step guidance to pass your review and get to market faster.
Permissions Assistant by Tython
Simplify security and permissions for Salesforce admins & consultants. Secure your data using head-to-head user comparisons, AI summaries, org-wide integration audits, and analyses that can span across time or even between separate orgs. Gain Powers & Save Hours. Visit Permissions Assistant on the AppExchange to start your free trial today.
ISV Forge
Accelerate Your AppExchange Success!
Sponsorships
Advertise on AppsemblyLine to elevate your brand and connect with a passionate community of leaders!
