Let me paint you a picture.
It's a perfectly good Saturday afternoon. You had plans. Real plans. Maybe you were going to finish that side project, maybe finally write some tests (lol), or at the very least touch grass for twenty minutes.
Instead, you're 4 hours deep into your Neovim config, you've rewritten your keymaps.lua for the third time this month, your lazy.nvim plugin list has grown by six plugins you don't fully understand yet, and your repo—God help you—is named neovim-final-final.
Not neovim-config. Not dotfiles. neovim-final-final.
Because the one before it was final, and that was a lie, and you knew it was a lie when you named it, and you did it anyway.
Hi. My name is Josh, and I have a configuration problem. I'm not in recovery.
"Just Use VS Code" — A Eulogy
I did use VS Code. For a long time, actually. It's fine. It's great, even. It has extensions for everything, it works out of the box.
But at some point, something shifted. I'd be in the middle of coding and I'd think: this editor doesn't feel like mine. It felt like renting an apartment versus owning a house. Everything worked, but none of it was mine. I couldn't knock down a wall. I couldn't rewire the kitchen. The landlord (Microsoft) was always one update away from rearranging the furniture while I slept.
So I did what any completely normal, well-adjusted developer does.
I nuked it. Installed Neovim. And fell into a rabbit hole I haven't climbed out of since.
Credit where it's due: a big part of what pushed me over the edge was
Catch you in the next one. 🚀
SOCIAL SHARE CARD GENERATOR