But I'll definitely prefer hiring someone who does. Sure, you can code in Vi without plugins, but why? Leave your elitism at home. We have deadlines and money to make.
Edit: The discussions I've had about AI here on Lemmy and Hackernews have seriously made me consider asking whether or not the candidate uses AI tools as an interview question, with the only correct answer a variation of "Yes I do".
Boomer seniors scared of new tools is why Oracle is still around. I don't want any of those on my team.
AI’s not bad, it just doesn’t save me time. For quick, simple things, I can do it myself faster than the AI. For more big, complex tasks, I find myself rigorously checking the AI’s code to make sure no new bugs or vulnerabilities are introduced. Instead of reviewing that code, I’d rather just write it myself and have the confidence that there are no glaring issues. Beyond more intelligent autocomplete, I don’t really have much of a need for AI when I program.
This is how I use it, and it's a great way for me to speed up. It's a rubber duck for me. I have a fake conversation, it gives me different ideas or approaches to solve a problem. It does amazing with that
The code it spits out is something else though. The code it's trained on in GitHub means it could be based on someone with 2 months experience writing their CS201 program, or a seasoned experienced engineer. I've found it faster to get the gist of what it's saying, then rewrite it to fit my application.
Not even mentioning the about 50% chance response of "hey why don't you use this miracle function that does exactly what you need" and then you realize that the miracle function doesn't exist, and it just made it up.
Sure, you can code in Vi without plugins, but why? Leave your elitism at home. We have deadlines and money to make.
Nothing elitist about it. Vim is not a modular tool that I can swap out of my mental model. Before someone says it, I've tried VS Code's vim plugin, and it sucks ass.
Please avoid double negatives. I'm not quite sure of the meaning of your sentence.
If you're saying I have issues using vim if I can't use it in an IDE, no, that's not how it works. If you use simple vim (not much more than knowing how to get in and out of edit/visual mode, and use hjkl for navigation), then it's fine. Once you get into more advanced vim features, though, the key presses in vim get picked up by the IDE first, so IDE shortcuts take precedence.
If someone were to learn vim inside an IDE and develops it organically as part of their flow, it'd be fine. If you already have a lot of standalone vim flow setup in your mind, it's a problem.