Post

When developing a large feature, writing Good Commits is hard.

And by Good Commits, I mean something like:

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.

So, naturally, here's what I do instead:

Latter commits overwrite work that was done in earlier commits and the story breaks. ⚖️

Jujutsu makes it easier to hop around commits and iterate quickly on compartmentalized changesets, but it's still effortful and I get averse. 🤖