

i host my dotfiles on GitHub, but any cloud provider or self-hosted git instance will do. otherwise, rsync, scp, or a good old fashioned thumb drive


i host my dotfiles on GitHub, but any cloud provider or self-hosted git instance will do. otherwise, rsync, scp, or a good old fashioned thumb drive

sorry it’s been a minute. i drank the emacs KoolAid because of posts like this years ago and happily switched back to Neovim after they added Lua config support

lol @ +BEGIN_SRC


this feels like a breaking change akin to macOS changing the Command key to bringing up a start menu because it confuses Windows users. platforms have differences, and this one is actually so tiny and inconsequential it feels like any ameliorated confusion will be offset by confusion of people that rely on it and use it. is this really the barrier to adoption?
other commenters have hinted at this, but the main point of most of the good advice is this: don’t use the system Python install (ie the one from apt) for development. uv is my go to, but the idea behind , pyenv, asdf, etc is the same. the underlying OS shouldn’t be an issue; you should be able to ship the code between OSs and build just fine, ideally.


generally speaking, i think it’s good practice to find several recipes and compare and contrast them. you’ll find opinions and get a sense for what the writer’s priorities are (quick, fewer dishes, what they usually have in the pantry, etc) and can figure out which writer has similar priorities to you. or just synthesize a recipe from those sources. this does require some technical know-how, but i think this is a good skill to have.


honestly, the brag document is a great takeaway. so many times people will subtly or implicitly question documentation or refactors, and when shit hits the fan and the readability refactor or documentation or logging/tracing PR becomes the clincher in quickly resolving the issue i love calling it out. documenting those cases themselves as a way to sell documentation and code quality to others feels like an amazing idea (if not exactly a “brag document”)
where i get into trouble is when i do a bunch of nixos-rebuild —switches between restarts and some state ends up hanging around, so next time i do a reboot that ephemeral state is gone and whoops no internet
normally it’s for syncing across machines, but it is convenient for setting up new machines. i use
chezmoiand Nix and some other tools to keep things in sync