2026–W21 #
It's been a week of kernel exploits: I've not enjoyed that.
My big work thing went well and I received much praise. My new work laptop for my new job has arrived and it's lovely (OLED 2.8K screen!) but also it was running Windows 11 which is unbearably bad.
(Luckily, I may Linux).
Put a front basket on my front rack of my MTB. So far, so good. Doesn't make steering too weird and I am more confident in it than a rear rack.
Trying out Gram as an editor (a Zed fork) and it has a pretty faithful Helix mode and nice language server integration. I find myself stuck between vim and hx and maybe this will help me get all the way to Helix-native while also having some IDE creature comforts where that makes sense. It's an aesthetically pleasing editor, tbh.
I am celebrating by writing some Go, refreshing my knowledge ahead of working somewhere that uses it. It's a little surprising to me how much my Go has atrophied. Unlike Rust (which also slides off my brain) I've shipped quite a lot of production Go code and at least some of it is still underpinning parts of Shopify -- so finding out that I can't easily just remember how to create an alias type and add functions to it is a little weird. Got there in the end, of course.
I've spent over a week with Ctrl swapped back to the Framework/Thinkpad default of the bottom-left key. I thought that I changed this because I found it too jarring going to "Ctrl-Fn-Super-Alt" when a Mac has "Fn-Ctrl-Super-Alt" but I just ... can't get used to it. I have no problem on an external keyboard which is "Ctrl-Super-Alt" so I think that it's less "Control must be in the bottom left" and actually my memory is "Control must me immediate left of Super" which is true on a Mac, on my external keyboard and on my Framework (when I enable the key-swap in the BIOS).
It just makes a little confusing for other people to use my laptops, but then that almost never happens so it's probably not worth worrying about.