Quote · Syntax - Tasty Web Development Treats
1019: LGTM, Ship It: The AI Code Review Problem
Where this was said
Exploring New Tools: Jujutsu and Beyond
At 16:20 · chapter starts 16:09
The next question arrives from someone who keeps seeing Jujutsu (JJ) promoted as a superior Git replacement. Wes opens with a sharp analogy: people explaining their JJ use case sound like someone who 'was tired of using super glue to keep spaghetti on my spoon, but this new spoon improves super glue retention by 50%' — solving a problem that shouldn't exist if you're using Git normally. Scott, who has researched JJ without yet adopting it, gives a fair-handed breakdown of its actual features: full Git compatibility (you and your teammate can use Git and JJ on the same repo simultaneously); an operation log that tracks every action including snapshots and merges, enabling a simple universal undo command; automatic staging (no more stash); and bookmarks instead of branches, making navigation between work states more fluid. Scott notes that committed JJ users love it, but newcomers often find the branchless mental model too jarring a shift. His overall verdict: interesting, but not a compelling enough reason to switch if you don't already have the problems it solves.
Jujutsu (JJ) is Git-compatible, offers a universal undo command via its operation log, and removes the concept of branches in favor of bookmarks. But every time someone explains why they switched, Wes hears someone who was just misusing Git — not someone with a genuinely unsolvable problem.
Jujutsu (JJ) version control can use Git as its backend, allowing different team members to use Git and JJ on the same project simultaneously without conflicts.
Jujutsu maintains an operation log of all revision history — commits, merges, snapshots — allowing users to simply run an undo command at any point.
Git was designed for humans making deliberate commits. AI agents commit every thought. The next version control system needs to capture every operation, every keystroke, and every agent conversation — and whoever builds that wins the next era of development tooling.
