is GitHub also going to start charging per second you stare at their diffing that takes a full minute to load

Gratz on new job

2. I want my nvim hacking loop to be very tight. kickstart-nix.nvim gives me a nvim-dev that works off a symlinked nvim config, and doesn't require the config to be hermetic. Great for tight hacking loops, and then I can commit and `nix-darwin -- switch` and I have my repeatable env again.

What I learned:
1. I don't want to write lua through writing nixlang. It's the worst part about nix for me, being a special language with really bad error messages.

Taking away the question of "When do I make a commit?" is HUGE. Also the ability to describe what I'm _going_ to do, and not what I _did_.

Can't wait to try and use #jj when I need to do actual work for pay, and not for saturday couch coding.

At a prior gig, I used gerrit and patch based review, along with git-repo. I spent a lot of time woking in detached-heads almost exclusively and lived in the reflog.

That *felt* like a good flow even though its an insane way to use git, and I think jj might be like that but good?

In the almost exactly 20 years (!!!) I've been using git, my workflows have changed a lot.

Today, I do a lot of interactive rebase, and stacking PRs in Github even though that sucks. Lots of amending, lots of faffing around with history to get things reviewable.

New thing is a beelink n100 to run my plex server. Does it have to be complicated? No. Should I make it complicated? Also no. Should it be an appliance? Yes. Will I complicate it? You betcha.