/home/daviwil/.dotfiles

I prefer tools that enable me to control everything primarily with the keyboard. When you work with words and code all day, reaching for the mouse switches your input modality and slows you down. Using GNU Emacs enables me to have consistent, convenient key bindings for just 80% of what I need to do on a daily basis. Another 15% is covered by using web sites and apps; Qutebrowser makes the web browsing experience a lot more keyboard friendly and seamlessly integrates with my Emacs workflow.

I don't want things on the screen that are unrelated to what I'm doing. My workflow focuses on a single main screen with an occasional secondary screen (my laptop) when docked. I very rarely display more than one buffer or window on the main screen at a time. Emacs makes it easy and fast to switch between open buffers (and workspaces in EXWM) so there's really no reason to have two unrelated things visible on the screen.

I display minimal information in my Emacs mode line (using doom-modeline) and I only display a small amount of computer status information in Emacs' tab-bar-mode.

I really don't want to use a program that doesn't support text-based configuration files. I also prefer tools that don't write out those configuration files on my behalf. This enables me to commit program configuration to source control (this repository) so that I can keep configurations in sync on every machine that I use.

Guix enables me to apply this principle to my entire system configuration, even sharing the same base configuration across multiple machines. This has provided me with a stable, consistent computing experience across the three machines I use on a regular basis.

To perfect my computing workflow, I choose tools that allow me to customize them to fit in smoothly with everything else. Emacs is the most faithful adherent to this principle as it allows you to intercept or replace the code for just about anything it does. For other programs, I like to use tools that are either scriptable by some means or enable to you call out to another process (or shell script) to gather information. Vimb and Polybar both do this, so it's pretty easy to integrate them into the rest of my workflow.