Trying jj with this blog's git repo

Current status: I’m trying Jujutsu, aka jj, to manage this blog’s git repo. I’ve used git since … 2011-ish? I tried jj once before but assumed it’s not worth the learning curve. My use cases are so simple these days, as I use git as a personal backup and sync tool rather than for collaboration with other people, which is where things get more interesting. But I recently learned my company’s Engineering department is moving to it. That made me stop and think … and ask Gemini if I should bother. Gemini told me: While jj’s greatest praise comes from developers managing massive “stacked PR” branching trees, its benefits for a single-developer, main-branch-only workflow are arguably even more dramatic. It fundamentally changes your daily relationship with your code. Okay, okay. Let’s not get carried away, buddy. But sure, I’ll try it. I’m using Steve’s Jujutsu Tutorial to learn the basics. Workflow example: splitting active changes into multiple commits While writing this post, I ended up…