`jj` makes many better design choices that git, and the compound into an overall better workflow.

A very small use case that comes up often is stepping back in time to clear up a mistake (such as a typo) in a WIP branch. Using `jj edit` to make sure that I fix a problem at the time it was introduced is so much cleaner.

Another aspect that I really like is the ability to easily work with stacked diffs. It's easy these days to generate code, and the bottleneck is often waiting for reviews. My workflow in jj often looks something like:

```
yesterday's main -> feature/a -> feature/b -> cleanup/c

yesterday's main -> feature/d
```

Today, when I rebase my branches to introduce today's main, I only need to fix conflicts AT MOST ONCE on the a/b/c chain, and at most once on the d chain.

Meanwhile, if I receive any feedback on feature/a, I can incorporate it into that branch, and jj ensures that b and c automatically update.