Biggest piece of advice, you don’t need to document everything you do in your life. If it’s info you might use in the future, a significant interaction or event, fun tidbit etc, add it in. If it’s just a casual conversation with someone that you don’t learn anything significant or it’s something that you’ll never link to or use again, just keep it as a memory.

I did a lot of over-capturing early on and got a lot of fatigue from it. Now my note making is as I run across things I’ll want to reference in the future (plans that were made, ideas to learn more about later, important phone calls/interactions, notes on articles, updates on projects, etc), with refinement to those ideas coming when I access them again later (or if I’m bored and have time). It’s no longer a drain to grow my PKM, it’s slower but much more meaningful info

Honestly, whatever works for you.

My preferred system is two big directories, one for your daily notes (dailies, journal, etc), and another for literally everything else.

This is how logseq is implemented, and can easily setup emacs org-roam to do it too. It’s very nice because you don’t need to worry about where to put something, throw it in your daily journals and get all the info down there, and link densely. If it’s about a specific topic, link to it and when you go to that topic you’ll see the info in the back links below (logseq does it automatically, emacs take a bit of config). You can then transcribe the important/summary/etc info from all of your aggregated back links into a single well thought out and planned document, or at least a single trimmed down one. Or, just leave all the info in the back links, whatever works best for you

It has org mode, but the links in logseq aren’t compatible with org-roam links, so either you use custom elisp to make logseq links into emacs compatible links and can’t follow links in logseq, or make emacs notes logseq compatible and can’t follow links in emacs.

Also, iirc logseq is planning to drop org mode support when they launch their database update, either that or have it available but not updated anymore.

I use bspwm and I really like the unicorne philosophy of the config files (bspwm controls your windows and such, sxhkd controls keybinds, two separate programs and config files. The bspwm config file is also just a bash file so you can add anything bash related to it easily.

This said, I love the dynamic workspaces on i3 and wish bspwm could replicate them. I don’t like i3 enough to switch to it purely because it’s also on x, but when Nvidia gets better Wayland support I’m definitely hopping ship to sway (i3 on sway basically)… Or when I’m able to swap my 3080 ti for an and gpu at a reasonable price

Quick note, duckduckgo has a free alias email forwarding service and it integrates with bitwarden

What are you using instead of emacs? I’m very happy with my doom emacs setup and it doesn’t feel slow at all imo

Have you tried running doom emacs in tmux on the remote server and accessing it with ssh? Doom emacs is all the good of an emacs environment, all the good of vim keybinds, and they worked in a decent amount of optimizations so it only loads the necessary stuff on demand (mine has a startup time of just over 1 second, slower than vim but barely an inconvenience). Can write a quick script to ssh copy (or git pull) your current configs on the server so you only have to maintain one set of configs if you want

scp ~/.config/doom/config.el username@server:~/.config/doom/config.el

Run emacs in tmux if you want to keep the emacs session open across multiple ssh sessions

Then I moved the microscope until it finds at least one, pick the first one from the new lever group, and my power takes care of throwing that first found/seen lever in the same instant as me throwing it in a normal set of levers

The first one that that guy sees, or the first one listed when they tell me what levers they have in the warehouse

They get smaller to show that they’re further away in the background not that they get infinitely small. If they were actually getting smaller, then sure, I grab an electron microscope, look at a field of levers, zoom until I see one, and pick that one, then somehow throw an electron sized lever, move to the next, smaller, physics defying lever group and just wait for quantum mechanics to do it’s thing I guess

This would apply if I had to pick based on the set of levers in each group. By picking the first one I see I get out of the muck of pure math, I don’t care about the set as a whole, I pick the first lever I see, lever x. Doesn’t matter if it’s levers -10 to 10 real numbers only, my lever x could be lever -7, the set could be some crazy specific set of numbers, doesn’t matter I still pick the first one I see regardless of all the others in the set.

Pure math is super fun, but reality is a very big loophole

The first lever I see in each group.

Even if my wife and I get our meal fully comped because the kitchen messed up or it took a long time (has happened a few times, college town. We never complain or get upset, the managers just come over and apologize then comp it), we qt least tip as if it wasn’t comped, if we liked our server and/or the food a lot (both, most of the time) then we tip the full amount of the comped meal. Without fail the servers have been surprised that we tip at all when that happens

I use vim keybinds (via doom emacs) for this sort of stuff if I’m doing it for personal projects, my professional work is all done in an online platform (no way around it) so it’s just faster and easier to throw the pattern and columns at the integrated chatgpt terminal rather than hop to a local editor and back

I use chatgpt semi-often… For generating stuff in a repeating pattern. Any time I have used it to make code, I don’t save any time because I have to debug most of the generated code anyway. My main use case lately is making python dicts with empty keys (e.g. key1, key2… becomes “key1”: “”, “key2”: “”,…) or making a gold/prod level SQL view by passing in the backend names and frontend names (e.g. value_1, value_2… Value 1, Value 2,… Becomes value_1 as Value 1,…).

Free: closed source, Dev can make it non-free any time they want, add monetization, ads, collect and sell data, change licensing, etc at any time and you just have to deal with it or switch software

Foss/open source: if the Dev tries to monetize, add ads, go private, collect/sell data, people will just fork a non shitty version and maintain that

Windows 98 has entered the chat.