You're not looking at the code?
Ask HN: How do you use Vim in the era of AI?
31–40 of 105 posts
Re: Ask HN: How do you use Vim in the era of AI?
#32I switched from using Vim as my primary editor to using Zed's Vim Mode. When you have a second process editing your project in the background you need an editor that can display those changes immediately without clunky buffer reloads. I've also customized Zed's UI to optimize for reading and reviewing code, and mostly adding notes or small focused edits, rather than writing entire files from scratch.
Re: Ask HN: How do you use Vim in the era of AI?
#33The intersection of people who like vim and ai is basically nil
Either way I'll happily be part of your `nil` category.
Re: Ask HN: How do you use Vim in the era of AI?
#34Re: Ask HN: How do you use Vim in the era of AI?
#35Definitely not a vim power user though. I just like writing markdown spec-ish prompts and opencode simplistic input box isn’t ideal for that
Re: Ask HN: How do you use Vim in the era of AI?
#361. /edit => opens in editor
2. /feedback => opens the last llm message in an editor so i can inline feedback. Think inline responses in email vs bottom posting.
3. /review => same as /feedback but opens up the diff so i do an inline review. Yes I still read the code it ships.
So basically in this flow vim becomes integral to doing anything involved.
Re: Ask HN: How do you use Vim in the era of AI?
#37I’m not using any AI. A lot of us aren’t. Vim has done me well for 30 years so I’m not going to throw that away to sharecrop on someone else’s land.
Re: Ask HN: How do you use Vim in the era of AI?
#38You're not looking at the code?
I'd even go so far at to say that if you're not writing the code yourself, you probably need to look at it even more than previously. Even before AI most of us read way more code than we wrote, that should still hold true.
Re: Ask HN: How do you use Vim in the era of AI?
#39I've noticed that my preferences for tools and languages is shifting as well. I'm happy to work with stuff that I previously would have not touched now because it would take me too long to get up to speed with languages, frameworks, etc. That stuff no longer blocks me from being productive. I still care about code quality, good design, etc. but a lot of that stuff doesn't require me to micro manage a code base. In the rare case I want to open something in an editor, I use vs code. I've removed a lot of the plugins in that as I'm not really using them any more.
I actually do reach for vi on the command line sometimes. But I've never been very good with it. I know how to do simple edits and save the file. I just never really got into it. I memorized a handful of key bindings somewhere in the nineties and that's it. I know some people that live in this editor and swear by it but for me it's just something that's there by default that is vaguely useful in a pinch if there's nothing else.