aquafunkalisticbootywhap

After being a vanilla vi then vim user for a long time before switching to neovim, I find folke’s which-key plugin to be very helpful. If i begin a key shortcut combination (or press my leader key), it shows me all the keys I can press next, and again after each additional step of a multi key sequence, and what each key sequence does. it works for mappings Ive added (usually basically the defaults for a new plugin) but also the standard built-in preset keymappings (see the ‘built-in’ plugins for which-key) for things like window mamagement and motions, using/viewing the registers (what did I just yank?), even spelling corrections, which helps you learn and build muscle memory. Often I dont use a specific mapping for a while and this helps me find it, especially when I group mappings by plugin, and/or prefix all mappings for a particular plugin or task with an additional prefix letter, so they all appear as options when I get as far as rembering “all my debugging mappings start with my leader key, followed by d.” By grouping tasks and plugins that way, I can press my leader key and see a list of where to go next, almost like browsing a menu hirearchy. “i dont remember which button to press after leader and d to toggle a breakpoint, but I know that’s where I’ll find it”

FYI it does work, but be aware youll need (sandboxed) google play services installed on at least one profile of your phone to connect a wearOS device

I played around with old iPads for a bit and then gave up. successful vendor lock for sure. I just wanted a home assistant front end without having to sign in to apple or use safari

etckeeper, and borg/vorta for /home

I try to be good about everything being installed in packages, even if Im the one that made the package. that means I only have to worry about backing up my local package archive. but Ive never actualy recreated a personal system from a backup, and usually end up starting from a fresh install, slowly adding back things from the backup if I missed them. this tends to cut down on cruft and no longer needed hacks and fixes. also makes for a good way to be exposed to new paradigms (desktop environments, shells, etc)

something that helps is daily notes. one file for any day Im working on my system and want to remember what a custom file, confg edit, or downloaded/created package does and why. these get saved separately and I try to remember to grep them before asking the internet

i see the benefit to snapshots, but disk space is expensive, and Im (usually) careful (enough) not to lock myself out or prevent boots. anything catastophic I have to fix is usually seen as a fun, stressful learning experience! that rarely happens anymore, for better or for worse

shoutout to USAA banking app that detected my root, but just showed a warning and allowed me to continue. that’s how it ahould be imho

because workers don’t collectively own the means of production.

not to be like that, but once some new hotness graduates from 2 people in a garage, the controlling interest is never the workers who have a vested interest in products, daily work (and a brand) they can be proud of, but investors with only short term profit on their mind. innovators- and inventors-turned-C suite executives jump ship when bought out, leaving the real meat and potatoes, the real work behind the brand, to be offshored, profit prioritized and picked clean.

buy from worker-owned co-ops. buy from local crafters and people deserving of the label ‘artisan’. flat out refuse to buy from brands that are a sad, hollowed out husk of their former selves. more importantly - most importantly - do what you can to keep your retirement investments away from quartly-profit mills who couldnt care less about workers or customers beyond raw sales numbers. and definitely, definitely never agree to work for them.