My Neovim Config Journey

I switched to Neovim six months ago. Here’s what I learned.

Why bother?

VS Code is fine. But when you open it 40 times a day, the startup time adds up. Neovim starts in under 50ms and runs everywhere — including SSH sessions.

My setup stack

• lazy.nvim — plugin manager
• nvim-lspconfig — LSP for Python, JS, Lua
• nvim-cmp — autocomplete
• Telescope — fuzzy finder (replaces Ctrl+P)
• nvim-treesitter — better syntax highlighting

The learning curve

Week 1: frustration. Week 2: muscle memory. Week 3: you stop thinking about keystrokes.

One tip

Don’t copy someone else’s full config. Build yours from scratch. You’ll understand what every line does.

Config repo

I keep mine at ~/.config/nvim/ and version it with Git. Changes are small and incremental.