/thoughts
insights, opinions, experiences, ...
ARCH.LOG #9: From Zed to Neovim (The Editor Journey): My keyboard-driven, terminal-first setup had one weak point: my editor, where my hand kept reaching for the mouse every time I needed to navigate or select code. Three weeks into learning Neovim with LazyVim, I finally understand why people use Vim - my hands don't leave the keyboard anymore, and I can edit code faster than I can think.
ARCH.LOG #8: Letting Go (Switching to Omarchy): Chrome is gone - I'm using Chromium now, not because I chose it but because I didn't choose to replace Omarchy's default. Turns out accepting 'good enough' instead of chasing 'perfect' freed up mental energy for things that actually matter, like shipping 2,000 lines of code last week instead of tweaking color schemes.
ARCH.LOG #7: Letting Go (Switching to Omarchy): I wiped my perfect setup - the one I spent two months building and breaking and fixing - and installed Omarchy in twenty minutes. Turns out someone else's 80% is better than my 100% when that 100% means I'm spending evenings debugging configs instead of shipping code.
ARCH.LOG #6: Config File Hell (And Why I Needed an Exit): NVIDIA drivers updated yesterday and broke everything - screen tearing, random crashes, three hours hunting down kernel parameters and config tweaks I barely understand. I came here to learn to code and build things, but instead I've become a full-time system administrator for my own desktop, spending more time maintaining perfection than actually shipping anything.
ARCH.LOG #5: Building My Perfect Setup: It took 40 days, but I finally built a system that feels like mine - every keybinding, every color, every animation configured from scratch and tracked in my dotfiles repo. But there's a problem: I'm spending more time tweaking configs than actually building anything, and 'just one more adjustment' is becoming my most-used phrase.
ARCH.LOG #4: X11, Hyprland, and WTF is a Window Manager?: I have a computer that boots into... nothing. Just a terminal, because turns out a graphical interface on Linux isn't one thing - it's layers I didn't even know existed, and I had to learn what display servers, window managers, and compositors actually do before I could see anything other than a command prompt.
ARCH.LOG #3: Going Bare Metal: The Arch Wiki installation guide sits in my browser - I've read it four times and I'm still terrified I'm going to brick my computer. But I didn't spend two weeks distro hopping just to chicken out now, so here goes: me, a command prompt, and a very long list of things I need to do manually.
ARCH.LOG #2: The Distro Hopping Disaster: I've installed Linux ten times in two weeks - Ubuntu, Mint, Pop!_OS, Fedora, Manjaro, Garuda, CachyOS, EndeavourOS - and I still don't know what I want. Turns out I wasn't learning Linux; I was shopping for Linux, looking for a distro that would magically teach me everything without any work.
ARCH.LOG #1: The Windows 11 Rejection: My computer wouldn't let me upgrade to Windows 11 - not because it's broken, but because Microsoft decided my perfectly functioning machine is obsolete. The rejection wasn't a problem; it was permission to finally try the thing I'd been curious about for years but too scared to commit to: Linux.