Disclosure: I'm an emacs user
It almost litterally is. Even busybox contains a vi clone. While I have encountered more systems without nano nor Emacs than I can remember. Plus, there is no excuse for learning the basic set of commands: i,ESC,x,u, and maybe navigating with the letters (which I'm not proficient at).
All that does is remind me that I haven't set nano as the default editor on that box and then I move on.
Any modeless editor should not cause trouble but vi (especially) is quite pernicious and the candidate would be just losing time.
But I agree, it should not be a show stopper.
(Emacs and vscode user here)
I love vi and set it as editing mode everywhere, nevertheless I accept that it might not be something people actively seek. If I was looking for a unix server admin then I would definitely assume they know vi.
While I don’t think vi is a showstopper, it would certainly be curious how a mid to senior engineer wouldn’t know how to use insert and quit in vi. This would make me think that a Windows only background never even meant connecting to a shell and having to view a file.
I’ve experienced lots of app developers who only use an IDE and don’t know how code is deployed or runs so they’ve never debugged a deployment, ever. They are in a big enough environment where that’s someone else’s job and they never have to talk with them.
That’s perfectly cool and folks will make a living and retiring in that world. But I don’t typically hire too many of those because I work in cross functional teams where the windows devs have to at least be able to understand and communicate with the Linux devs, and vice versa. That means having basic user level skills like two commands in vi, because it is almost always available on Unix systems. And frequently the only one allowed.
I think folks confuse this as meaning that people who don’t know vi are dumb, they aren’t. They could be geniuses who just don’t need to know vi. But for many types of interviews, it’s a super easy screening question that makes me follow up with more questions if they answer “I have to google.” It would be similar if a developer didn’t know cd or had never seen notepad or something.
For a Linux desktop user, including devs, I wouldn't consider not knowing vi to be that odd, given that other editors commonly ship or are a single install command away. For someone not working on Linux, it's even less expected.
My point is that you can be a perfectly nice programmer with a full career without being really good.
A bad engineer is happy that he has learned framework X and doesn't feel he needs to learn anything else.
Putting the Linux admin candidate in front of an xcode window is a quick and to find out where he stands. If he looks totally lost, he is definitely a 10x guy.
> Putting the Linux admin candidate in front of an xcode window is a quick and to find out where he stands. If he looks totally lost, he is definitely a 10x guy.
They are or they are not? Judging by the previous paragraph this sentence seems odd.
And I would argue that you could apply that to all programmers
I've interviewed a lot of people in Amazon and always offered choice between at least 4 editors.
If you cannot pass a coding challenge the problem is not in the editor.
Did you read the next sentence? The Windows guy that chose to use vi was hired.
If you've been writing a lot of software, I would expect you to be good at actually putting the characters into a file and moving them around therein. I would be very suspicious of someone who claimed to be a master carpenter but couldn't drive a nail cleanly. Muscle memory is a real thing, and the mechanics of a task matter. What is the point of all our fetishization of editors and keyboards and such if not to smooth the transition between brain and paper?
This isn't even always a matter of candidates operating in an unfamiliar environment. Even on their own personal computers, in the editor they presumably use for work, I see a lot of flailing.
Do yourself and the candidates a favor and step back from it to allow yourself to lose such prejudices.
>I open gedit for them to use, with the offer that they can use any other Unix editor they like.
I wonder if he required using vi when that Windows programmer interviewed or if the Windows guy chose to use vi.
"Editor Flailing
It’s funny how many people can’t edit text on any machine but their own. I tend to interview people on a laptop running Ubuntu, and I open gedit for them to use, with the offer that they can use any other Unix editor they like. Most can barely navigate gedit, and it’s stupid simple.
Don’t ever let yourself get hung up on the editor. If you can’t figure out the magic command keys to indent code the way you like, just press the damn space bar and indent it yourself. Flailing in the editor wastes time."
Talk about an arbitrary condition. Sure, being adaptable and/or pragmatic with respect to tooling is a nice thing for your candidate to have, but to prioritize it at a similar level to knowing what your company does?! Are you really going to hire the incompetent-but-familiar-with-emacs Linux user over the capable-but-rigid Windows dev? Unless you're looking for an SA or full-stack dev, this seems rather arbitrary, especially considering the availability of plenty of cross-platform, fully-featured editors.