I've been a little spotty with writing and posting these the past few days. It's often a common pattern with me, that I start a routine in a way that makes the process easy (these were initially pretty terse and honestly, not that interesting), then decide to up the ante a little bit. Then it becomes a little more of a hassle/cognitive demand to do it every day. I will also do this thing occasionally where I procrastinate by doing something else that's productive. It's probably better than what I did in college (Netflix and Pokémon) but the outcome is similar-ish.

Nix (repo)

How common of an experience is it to write and update configurations while not having a firm grasp of the syntax or understanding the concepts behind your changes? There are a lot of features and comforts being added to my configuration that I read somewhere and don't conceptualize and brute force into working. This is directly a reference to how I implemented sops-nix for my git provider ssh keys.

To remedy my feeling of being in the dark, I've spent a lot of this morning editing and reviewing my notes.

I plan to migrate the configuration of my mac mini to this setup next weekend, because if I do it anytime during the week it'll take up an entire day.

Beacon (code)

I've added some more refactoring features behind the execute command LSP action. It's amazing how powerful this can be and makes sense that it's not implemented in a lot of LSPs. There's a fair bit of tree traversal and position calculation required. The integration of a control flow and dependency graph can be complex too. Even with prior art that has these pieces, putting them together for refactoring has been hard.