> This is similar to the red squiggles enjoyer, [..] I tend to just write my code so that I know where everything is, keep it small, and name things in a way that matches how I'm coding.
An interesting take, I do aim for the same style (especially as LSPs can break) but in shared code bases this almost always seems to be an issue.
Ime it mostly comes down to the other collaborators having a different naming sense. Keeping it small similarly can be challenging as code grows organically and debt is accumulated. At that point code navigation (especially workspaces wide goto and fuzzy symbol search) becomes immensly useful for fast navigation.
zem•5mo ago
I used to be a vim-without-lsp dev too, but "jump to definition" really is worth setting up the lsp integration.
dbalatero•5mo ago
I agree, I'm a neovim maximalist myself and think these things are worth setting up - good autocomplete, Telescope/fzf-lua, LSPs, etc. To each their own though, I'm sure I could still be effective with Zed's setup as well.
dingua•5mo ago
I really respect such POV, I admire the aspect that we are considering coding as an art more than as a job. I wish we had the time to get a deep conversation about it..though the article itself is inspiring enough, thanks!
c0balt•5mo ago
An interesting take, I do aim for the same style (especially as LSPs can break) but in shared code bases this almost always seems to be an issue.
Ime it mostly comes down to the other collaborators having a different naming sense. Keeping it small similarly can be challenging as code grows organically and debt is accumulated. At that point code navigation (especially workspaces wide goto and fuzzy symbol search) becomes immensly useful for fast navigation.