Defeating Git Rigour Fatigue with Jujutsu
Scored daily by a customisable AI persona to surface the most relevant engineering leadership news.
Jujutsu vcs guide, extremely actionable and directly matches developer experience interests.
Jujutsu (jj) alleviates 'git rigour fatigue' by allowing developers to create messy commits during feature development and later reorganize them into clean, logical history using `jj new` and `jj squash -i`. The technique—informally called 'Doing Commits Like A Big Pile Of Laundry'—involves creating an 'everything commit' from all work, then interactively sorting hunks into predefined empty commits, avoiding the mental overhead of maintaining sequential commit discipline. A tradeoff is that intermediate commits may not compile until the final reorganisation is complete.
Try jj's squash-interactive workflow to defer commit tidying until the end of a feature, letting you write messy in-progress commits without breaking the narrative of your pull request.
For a Solutions Architect focused on developer experience and platform engineering, this workflow reduces cognitive load and friction in version control, enabling faster iteration on large features without sacrificing commit quality in code reviews.
defeating git rigour fatigue with jujutsu computers This post assumes a basic level of familiarity with the jujutsu version control system . If you haven't used jujutsu, you'll still get the gist of the idea, but I recommend reading Steve's Jujutsu tutorial after. When developing a large feature, writing Good Commits is hard. And by Good Commits, I mean something like: define types add DB functions server CRUD client API client UI This allows reviewers to step through your pull request in small bites, with each set of changes scoped to a single aspect of the feature.