News for hackers. Stuff that matters.
Re:Technical Interview Performance by Editor, OS, and Language by dtran on Tuesday September 19, 2017 @01:53PM (#15287000)
(Longtime emacs user but have now used sublime text for several years)

Super interesting post, Mike! Not surprising that emacs/vim users tested better since use of those is likely correlated with having programmed for longer or having programmed from earlier in life before some of the other editors even existed. Would love to see it normalized by years programming. Also, insert joke about how using emacs or vim probably led to natural selection weeding out all but the most committed programmers or how the bad vim programmers didn't start their Triplebye interview because they're still trying to figure out how to toggle back to command mode to exit. :stuck_out_tongue_winking_eye:

I was surprised to see such a big difference between PyCharms and Sublime. Would love to see a language breakdown for generic text editors like Sublime and Atom and compare python interviewees who used Sublime to python interviewees who used PyCharms. I also wonder if there's some confounding variable since AFAIK there's no free version of PyCharms whereas there are free versions of Sublime and Atom, so an interviewee who has a PyCharms license likely uses it in a school or professional setting.

Re:Technical Interview Performance by Editor, OS, and Language by mywittyname on Tuesday September 19, 2017 @03:13PM (#15287886)
Personally, I think it speaks to the ability to learn. Vim and Emacs are borderline torturous for beginners and it's easy to give up. The ability to push past insurmountable difficulties is likely highly correlated with programming performance (since most of us need to do that often).
Re:Technical Interview Performance by Editor, OS, and Language by mettamage on Tuesday September 19, 2017 @03:44PM (#15288136)
I don't know about emacs (never tried it), but I really disagree with vim. I keep saying this on Hacker News over and over again but go to your terminal, type in vimtutor and 30 minutes later you can survive in vim and not flip out anymore.

Mastering vim or becoming pretty good in vim, seems quite a bit more difficult.

I've given up on vim 5 times, until someone on HN suggested me vimtutor. It really taught me the value in good educational content.

Re:Technical Interview Performance by Editor, OS, and Language by Jtsummers on Tuesday September 19, 2017 @09:48PM (#15290134)
C-h t (ctrl+h then t). This will bring you to the emacs tutorial. It's similar to vimtutor but covers primary emacs usage.
Re:Technical Interview Performance by Editor, OS, and Language by rnet85 on Wednesday September 20, 2017 @03:37AM (#15291533)
This is exactly his point. Taking the initiative and spending time to learn something like vim, not giving up, looking for tutorials and working through them just shows the person is willing to endure some hardship to gain something good in return.
Re:Technical Interview Performance by Editor, OS, and Language by bJGVygG7MQVF8c on Monday September 25, 2017 @11:36AM (#15331287)
Yup.

> insert joke about how using emacs or vim probably led to natural selection weeding out all but the most committed programmers or how the bad vim programmers

uh.... /joke/?

Re:Technical Interview Performance by Editor, OS, and Language by saiprashanth93 on Wednesday September 20, 2017 @02:52AM (#15291355)
Learning Vim using vimtutor is one thing for people coming from editors like Sublime/Atom, but setting up vim so that autocomplete/File Tree/FileSearch work like expected is a whole different ball game.
Re:Technical Interview Performance by Editor, OS, and Language by empthought on Wednesday September 20, 2017 @12:38PM (#15295690)
And at that point one may as well leverage the work of the hundreds of developers at JetBrains or Microsoft and use a real IDE.
Re:Technical Interview Performance by Editor, OS, and Language by jackmott on Tuesday September 19, 2017 @03:56PM (#15288235)
you need to master it though before it stops being a productivity hindrance if you have already mastered an IDE with first class support for your language.
Re:Technical Interview Performance by Editor, OS, and Language by quickthrower2 on Tuesday September 19, 2017 @04:03PM (#15288304)
That's why I gave up on Vim at work vs Visual Studio.

But it's my go to for Haskell projects.

What I like best about vim is the startup speed and fewer reaches for the mouse. I do like using the mouse to select a large block of text to indent tho!

Re:Technical Interview Performance by Editor, OS, and Language by scruple on Tuesday September 19, 2017 @08:30PM (#15289866)
VsVim is pretty decent if you're using Visual Studio. It gives you modal editing and support for a healthy subset of vim keybindings. I was doing some C#/.NET work a couple of years ago and VsVim was a lifesaver.
Re:Technical Interview Performance by Editor, OS, and Language by caconym_ on Tuesday September 19, 2017 @07:05PM (#15289519)
I use Vim everywhere and if I want IDE stuff I use VSCode at home and IntelliJ IDEA at work but you can pry my Vim bindings from my cold dead hands regardless of the editor I'm using. Putting in the time to learn (it wasn't even that long until I was productive again, maybe one day of work) is one of the best decisions I ever made.
Re:Technical Interview Performance by Editor, OS, and Language by vram22 on Tuesday September 19, 2017 @04:07PM (#15288332)
>Vim and Emacs are borderline torturous for beginners and it's easy to give up.

Hardly so, IMO. Plus - and I assume here that you are talking here mainly about developers (using programming languages) and maybe web designers (using CSS/HTML/etc.) - the complexity of vi(m) and emacs can hardly be called higher than those dev and design technologies, except, maybe, for the use of advanced editor features and scripting of those editors in VimScript or ELisp.

Anyway, FWIW, I had published this article (a vi quickstart tutorial) in Linux For You magazine some years ago, after I first wrote it for some Windows sysadmin friends of mine, who were given additional charge of a few HP Unix boxes. After using the tutorial, they told me it helped them to quickly come up to speed on the basics of using vi (the predecessor of vim).

The tutorial is available here; it is short and easy to digest:

https://gumroad.com/l/vi_quick

Edited for wording and typos.

Re:Technical Interview Performance by Editor, OS, and Language by rnet85 on Wednesday September 20, 2017 @03:40AM (#15291545)
Thing is you don't need such tutorials for other text editors, you know how to use them intuitively. This itself is a barrier for entry for most people, people who manage to cross this barrier prove they've some initiative and motiviation to spend time in learning something that makes them more productive, they're more likely not to shy away from obscure tasks which may appear difficult on the surface.
Re:Technical Interview Performance by Editor, OS, and Language by vram22 on Wednesday September 20, 2017 @07:18AM (#15292488)
That's a good point. I did read similar comments to yours in this thread (such as the nearby one by andrewstuart2, and others), before posting about my vi tutorial, and agree with the general argument stated. I've grown from scratch in my own career by the same method you and others describe, i.e. doing a lot of self-study, trying out stuff a lot, poring over tech docs and books a lot (used to buy used ones earlier, when I could not afford too many new ones), borrowing from libraries, etc.

Edit: And have always recommended such an approach to younger developers and aspiring ones, when they ask me for advice, which sometimes happens. Basically tell them to learn as much as you can and invest in your future (with study effort, not only money) for the long term, not just for quick immediate gains.

Re:Technical Interview Performance by Editor, OS, and Language by andrewstuart2 on Tuesday September 19, 2017 @03:40PM (#15288105)
I think it also speaks to the ability to look beyond short-term pain to the long-term benefits, as you alluded to in your third sentence. Just because something is foreign and difficult should never be enough to discount the best, most efficient long-term solution. Powering through the barrier to entry with your mind on the long-term is necessary for success in engineering disciplines, and also happens to be required for proficiency in daily use of these editors.
Re:Technical Interview Performance by Editor, OS, and Language by bigger_cheese on Tuesday September 19, 2017 @08:00PM (#15289743)
>Vim and Emacs are borderline torturous for beginners and it's easy to give up

I really do not understand where this belief comes from. I learnt Emacs as a beginner in the early 2000's when I started university I'd never done any programming before (I'd also never used Unix before) our course was taught on Sun Solaris workstations and emacs I had many frustrations at the time I remember cursing Solaris and the stupid GUI it had (CDE) but never emacs - emacs just worked not sure what is supposed to be torturous about it.

Nearly 20 years later I still use Emacs daily it's one of the programs on my computer I probably "couldn't live without". Maybe at this point I'm just a hostage to my tools but i'm too old and too familiar with emacs to bother trying some other editor out - what do people use now sublime text? (if the article is accurate) I've never heard of it before I don't know anyone here at my work who uses it (I am an engineer not a software person though) could be a generational thing I'm in my mid 30's and one of the younger people at my work so maybe all the "cool" Mac kids use it or something...

Re:Technical Interview Performance by Editor, OS, and Language by bitwize on Tuesday September 19, 2017 @09:25PM (#15290069)
There is documentation of secretaries not only learning how to use Multics Emacs in the 1970s -- a much more primitive version than what prevails today -- but also how to extend and customize it using Lisp. (Multics Emacs was the first Lisp-extensible Emacs.)

It's not torturous to learn Emacs. But Emacs doesn't work like a standard Windows/Mac app, and today we have fewer professional developers willing to make it past the initial rejection phase of "wellp, this is weird".

And yes, today people use Sublime Text, something like Atom, IntelliJ, or -- for hipster cred -- vim. Emacs is apparently retro enough to be a total gonk for new users but advanced enough to not be redeemable for whuffie in hipster circles. Vim closes that gap.

Re:Technical Interview Performance by Editor, OS, and Language by AlexCoventry on Wednesday September 20, 2017 @01:29AM (#15291072)
Got a pointer to the documentation?
Re:Technical Interview Performance by Editor, OS, and Language by bitwize on Wednesday September 20, 2017 @11:31AM (#15294864)
http://multicians.org/mepap.html

This actually appeared on Hackernews a couple of times, which is how I found it. Money quotes:

"It was soon found that Emacs could be taught within minutes or an hour to those with no technical experience at all." (referring to TECO Emacs actually but applicable to Multics Emacs)

"Non-technical personnel have been observed to acquire enough knowledge of Lisp to extend Emacs for only this purpose."

"While ITS TECO code is quite baroque, and accessible to only a few experts, the extension language of Multics Emacs is sufficiently natural and simple to learn that non-technical personnel have successfully written and debugged non-trivial extensions."

Re:Technical Interview Performance by Editor, OS, and Language by msla on Tuesday September 19, 2017 @02:04PM (#15287160)
Using Emacs and/or Vim is also a test of how much you care, primarily because they're not the default anymore, so anyone who uses them cares enough about their programming environment to use a non-default editor, and one which has a rather higher barrier to entry than most at that.

(Although, to be honest, using the GUI version of GNU Emacs as a Notepad replacement is possible: Just ignore the keyboard commands and interact solely via the menu up top. You even get access to at least some neat major modes this way.

Still, Emacs isn't the default, so anyone using Emacs probably knows why, and won't be the kind of person to use it without getting more out of it.)

Re:Technical Interview Performance by Editor, OS, and Language by pavon on Tuesday September 19, 2017 @06:31PM (#15289379)
My experience is the opposite. The reason that I use vim is because I frequently have to work in environments that I ssh into, where X forwarding is blocked or very poor due to latency. It became too painful to constantly switch back and forth between vim, emacs, eclipse, netbeans, etc, so I gave up and settled on the lowest common denominator.
Re:Technical Interview Performance by Editor, OS, and Language by defined on Wednesday September 20, 2017 @12:04AM (#15290749)
Not to mention that many remote server environments may not even have X installed, or graphics cards, for that matter. I started using vi for much the same reason you did, having to troubleshoot via ssh (and telnet before that) in many variants of UNIX (tm) systems. When I got hold of Vim it was like Christmas for me.

I started learning emacs some time back, but the learning curve (and fighting against Vim muscle memory) vs. needing to get work done for money soon convinced me to try again another day.

Re:Technical Interview Performance by Editor, OS, and Language by AlexCoventry on Wednesday September 20, 2017 @01:32AM (#15291080)
Emacs works fine in no-X environments, FWIW. You're more likely to find vi just works without installing anything extra, though.
Re:Technical Interview Performance by Editor, OS, and Language by komali2 on Tuesday September 19, 2017 @02:13PM (#15287262)
I dunno man, I care enough to spend a big chunk of my free time improving my code ability. Thing is, I find it easier to use hotkeys in vscode than in emacs. I'm trying both right now and vscode just seems to allow me to do the things I want to do without like learning lisp or something.

In terms of "caring," I care enough to learn literally all of the hotkeys available by default in vscode, including some I added and changed. I'm a f'n beast in that IDE :P

Re:Technical Interview Performance by Editor, OS, and Language by craftkiller on Tuesday September 19, 2017 @02:49PM (#15287653)
That's great, but I think you hit on exactly the point the parent was making: to use emacs / vim effectively, you need to do things like learn lisp or spend countless hours tinkering and customizing. IDEs like vscode already come with some great defaults so it gets the full gamut from newbies to gurus. I think the parent was just saying that the emacs / vim group doesn't have the low end of that gamut watering them down.
Re:Technical Interview Performance by Editor, OS, and Language by marcosdumay on Tuesday September 19, 2017 @03:16PM (#15287915)
Everybody that is using emacs cares does not imply that everybody that cares is using emacs. It's a common fallacy, and it is one of the few that remain important even on non-boolean logic.
Re:Technical Interview Performance by Editor, OS, and Language by deong on Tuesday September 19, 2017 @04:52PM (#15288699)
"Emacs -> Cares, therefore Cares -> Emacs" is a form of abductive reasoning. It's only a logical fallacy if you treat it as though logic guaranteed the inference was true. If you treat it as, e.g., input helping to form priors in a Bayesian model, it can be useful information.

Let's say you have 100 programmers. 20 of them "care". Of the 100, 5 use emacs. P(emacs) = 0.05. If all emacs users care, then P(emacs|care) = 0.25. If I wanted to model this phenomenon, I shouldn't ignore the correlation just because it's not perfectly causal.

Re:Technical Interview Performance by Editor, OS, and Language by hacking_again on Tuesday September 19, 2017 @05:15PM (#15288880)
Or in plain English, if you care then there's a greater chance you'll be using Emacs.

The fallacy if any is assuming likeliness implies implication. This is commonly known as stereotyping, but it's perhaps more clearly described as generalizing a group stereotype to the entire group.

Re:Technical Interview Performance by Editor, OS, and Language by bJGVygG7MQVF8c on Monday September 25, 2017 @11:41AM (#15331328)
#problematic (and, incidentally, incorrect) mansplaining (regardless of your actual self-reported gender)

"stereotyping" is a floating signifier, and arguably in common usage doesn't merely signify hasty generalization.

Re:Technical Interview Performance by Editor, OS, and Language by quickthrower2 on Tuesday September 19, 2017 @04:06PM (#15288327)
True but this topic is more about correlation and prediction.
Re:Technical Interview Performance by Editor, OS, and Language by marcosdumay on Wednesday September 20, 2017 @10:28AM (#15294079)
I do really hope nobody is reading that article thinking about prediction. It's completely full of weak proxies that will lose any predictive power as soon as they are used.

(And that's also why you care about causation even if you are only looking for prediction, because you don't want your proxies to change their meaning as soon as you act on them.)

It is indeed full of correlation that can unmask interesting facts if studied further. And the GP complaint is meaningless if viewed from that angle, so I do really think he was talkinga bout causation.

Re:Technical Interview Performance by Editor, OS, and Language by eanzenberg on Tuesday September 19, 2017 @02:40PM (#15287562)
I use emacs, have a .emacs file that I carry around with me, and have no idea how to write lisp.
Re:Technical Interview Performance by Editor, OS, and Language by jhgb on Tuesday September 19, 2017 @02:56PM (#15287736)
Well, I do have an idea how to write Lisp but I still never got the hang of Emacs Lisp in particular. (But that may have something to do with the lack of actual effort on my part, admittedly.)
Re:Technical Interview Performance by Editor, OS, and Language by metaobject on Tuesday September 19, 2017 @06:52PM (#15289464)
Long time emacs user here with a .emacs which is highly customized and is updated by me frequently. I recently added (not sure what took me so long) code to automatically install packages which are missing (for instance, if I'm starting emacs on a new system).

Love all lisps, including elisp.

Re:Technical Interview Performance by Editor, OS, and Language by _asummers on Tuesday September 19, 2017 @07:30PM (#15289641)
If you use use-package, you can add ":ensure t" to the configs to accomplish this same thing. If you're not using use-package, you should be :) . Example use:

    (use-package unfill
      :ensure t
      :defer t
      :commands (unfill-region unfill-paragraph unfill-toggle)
      :bind ("M-q" . unfill-toggle))
Re:Technical Interview Performance by Editor, OS, and Language by omaranto on Tuesday September 19, 2017 @09:15PM (#15290034)
I'd recommend counting how many of your use-package forms have :ensure t and how many don't. If more have it than not, instead (setq use-package-always-ensure t).
Re:Technical Interview Performance by Editor, OS, and Language by todd8 on Wednesday September 20, 2017 @03:15AM (#15291451)
Hey thanks, I didn't know about use-package-always-ensure.
Re:Technical Interview Performance by Editor, OS, and Language by hashkb on Tuesday September 19, 2017 @02:22PM (#15287360)
You don't know what you're missing. Want to be a real beast? Learn vim and emacs, both. You want an editor where "literally all the hotkeys" is literally meaningless.
Re:Technical Interview Performance by Editor, OS, and Language by coldtea on Tuesday September 19, 2017 @02:32PM (#15287475)
>You don't know what you're missing.

Or it's diminishing returns, and most of it is busywork (fiddling with settings) and the pride of customization -- as opposed to any real tremendous productivity gains.

And I say that as someone who've used Vi(m) for 15+ years in platforms ranging from SunOS (pre Solaris), to Linux, Windows and OS X. I've also fiddled with Emacs for a year or so before (in uni) but it never really stuck. I use ST3 and Vim (terminal sessions) now and don't find Vim offering any huge productivity boost.

For all the folklore it's just an editor with some nice ideas, and a lot of random stuff throw in stolen from this or that earlier environment (read how Joy came up with vi).

Re:Technical Interview Performance by Editor, OS, and Language by aeorgnoieang on Tuesday September 19, 2017 @03:33PM (#15288045)
> don't find Vim offering any huge productivity boost

Really? I feel so much faster with Vim bindings. Watching other people try to edit text even with OS or other-editor bindings, let alone just selecting text with a mouse, is very frustrating.

I know other editors have bookmarks, and I imagine they might work as well as in Vim. But, besides Emacs, in what other editors can you 'delete everything up to the next `=`' or 'delete everything from the current cursor position to the start of the third word (to the right)'.

Gah – even cutting and pasting more than a line or two is so much easier in Vim than anything else.

And that's just editing text. Editing code is even harder for me! Trying to remove a 'word' in a long camelCase variable without being able to jump to a letter or a search pattern consists of hitting way too many arrow keys.

Re:Technical Interview Performance by Editor, OS, and Language by coldtea on Tuesday September 19, 2017 @04:04PM (#15288314)
>Really? I feel so much faster with Vim bindings.

I never felt typing speed or special text transformation shortcuts being my limiting factor.

At the end of a day, I'd have at most written 200 or 500 lines of code, and removed as much. Most days less.

And I don't write, re-edit and discard 10,000 lines in the process of crafting those new ones.

Speed of navigating between files (which is even better in ST than in Vim, vim, at least on the Mac, takes more 100s of ms to open a file, and NerdTree is crap) and finding the stuff I want matters more to me.

>I know other editors have bookmarks, and I imagine they might work as well as in Vim. But, besides Emacs, in what other editors can you 'delete everything up to the next `=`' or 'delete everything from the current cursor position to the start of the third word (to the right)'.

That a find at best a slight convenience of marginal utility.

My problem while coding is rarely "if I could delete until the next = more easily" but "what algorithm should I use", "What was the person who wrote this smoking" and "where's the documentation for this API".

I also don't buy the "but doing it with a shortcut/motor skills frees my mind from having to think about editing etc". As I've said, I've used Vim for 15+ years (still do, a decade after every time I'm in a shell). I've known all these shortcuts, used them, etc. Haven't seen it make any great difference in that respect. I'd take better code navigation, linting support, etc over text wrangling features any day.

(Besides I can do it just fine in ST anyway with Vintageous/Six/etc).

Re:Technical Interview Performance by Editor, OS, and Language by deong on Tuesday September 19, 2017 @04:58PM (#15288747)
I think he probably chose his words fairly carefully: "feel so much faster".

I don't think anyone argues that they can ship a piece of software noticeably faster using Vim or Emacs. Like you said, we're never limited by editing speed. But it's also true that you're not figuring out what code to write one character at a time. You spend most of your time looking at the code, figuring out what to do next. But once you've decided that, there is a little burst of activity during which the limiting factor actually is the motor skill of executing that desired action. In theory, all the little savings might add up, but again, I don't think anyone seriously argues that. I think it's much more that that microburst of activity felt less frustrating while they were doing it.

Re:Technical Interview Performance by Editor, OS, and Language by aeorgnoieang on Wednesday September 20, 2017 @11:32AM (#15294869)
We're definitely writing past each other.

> I never felt typing speed or special text transformation shortcuts being my limiting factor. > > ... > > Speed of navigating between files (which is even better in ST than in Vim, vim, at least on the Mac, takes more 100s of ms to open a file, and NerdTree is crap) and finding the stuff I want matters more to me.

I wasn't making any claims about the benefits of Vim bindings for my job as a whole. But why stop there? It's probably also not the "limiting factor" for me as human being.

But it's definitely a limiting factor when I'm writing and editing text.

> I also don't buy the "but doing it with a shortcut/motor skills frees my mind from having to think about editing etc". As I've said, I've used Vim for 15+ years (still do, a decade after every time I'm in a shell). I've known all these shortcuts, used them, etc. Haven't seen it make any great difference in that respect. I'd take better code navigation, linting support, etc over text wrangling features any day. > > (Besides I can do it just fine in ST anyway with Vintageous/Six/etc).

Above is even more that's besides the point I was making. I'd take good code navigation over Vim key bindings too. I wasn't saying Vim key bindings are better than anything other than not having them.

And then you basically make my point for me:

> (Besides I can do it just fine in ST anyway with Vintageous/Six/etc).

I do that too; not in ST, but in the IDEs, etc. that I use (e.g. Visual Studio, SQL Server Management Studio, Google Chrome). I assume you do for the same reason I do, i.e. you like the keybindings. I also find the keybindings generally useful and faster than not having them.

I do agree with the gist of your comment that Vim itself isn't particularly great compared to tools with features like code navigation. I don't use any Vim plugins for example tho I've tried a few.

Re:Technical Interview Performance by Editor, OS, and Language by splintercell on Tuesday September 19, 2017 @06:07PM (#15289238)
> I never felt typing speed or special text transformation shortcuts being my limiting factor.

You don't because the purpose of all the actions you take while editing text is to not think about it. As a non-vim users, you have trained yourself to not think about the time you spent editing text. You want to move an object of options from one file to another file and move it to another object (something which I did moments ago), then the moment you come to the conclusion that you need to make that change, you start using your mouse, select the object, Ctrl-C, then move to the other file, Ctrl-V, and press the shortcut to auto format. But you don't think about it any more than you think about switching windows when moving from one app to the other.

In vim too I probably think about it no more than you do about your own text editing, but with vim, I don't press modifier keys, I don't reach out for mouse, and opening a file is the same speed as IntelliJ (an editor my coworkers use), using Ctrl-P, if not faster. Traversing files is much faster. Splitting screen and navigating is a billion times faster than what you can achieve on any of these editors. All without using the mouse or modifiers.

But these are only small benefits when compared to the biggest difference I've seen between Vim/Emacs users vs non-Vim/Emacs users. Take for instance, few minutes ago I was doing pair programming with my coworkers, and I noticed that there were thousands of productivity shortcuts that he wouldn't use, and he is not the only one, majority of non-vim using people I've met, fail to make use of these productivity enhancements.

* Pressing Ctrl-C/X without selecting text just cut/copy the whole line. * Pressing double click on a line selects the word, triple click selects the whole line (or paragraph in text) * Using Alt-Tab to switch windows * Ctrl-Backspace deletes the whole word/token * Ctrl+Arrow key for navigation * Split Screen, nearly all their editors support split screen functionality, but opening multiple files in multiple panes is like crazy person talk

Even with this minor experience I have with their editors, I look like a magician using their IDE. Not to mention how slow their editor is while trying to help me by auto-completing. I was done typing the name of the class before their auto-completion kicked in. You call that slight convenience of marginal utility, but to

My point is that, productivity enhancements is a desire people have, which makes these people to move towards Vim/Emacs. For the people who don't even use Ctrl-A to select the whole text, they fail to see what they're really capable of doing on their editor.

> As I've said, I've used Vim for 15+ years (still do, a decade after every time I'm in a shell). I've known all these shortcuts, used them, etc. Haven't seen it make any great difference in that respect.

Considering you complaint about speed of navigating between files, I highly doubt that you know "all these shortcuts", because even if you do, the philosophy of vim is to keep optimizing your workflow, so you create a shortcut for shortcuts. I think it would be a cool idea to hold competitions where two people are given a codebase, and their own completely configured editor on the same machine with same processes running and then they are asked to do a number of tasks, like open UserController.js, UserView.html, UserService.js and refactor a variable and change some data.

Re:Technical Interview Performance by Editor, OS, and Language by coldtea on Wednesday September 20, 2017 @07:09AM (#15292429)
>Considering you complaint about speed of navigating between files, I highly doubt that you know "all these shortcuts"

You can doubt it, but you'll be wrong :-) Note that I'm not speaking of navigating between already OPEN files (I know how to move between splits, maximize them, etc), but between files IN the project I'm working with. Vim just takes longer for those tasks and gives worse overview/feedback on which they are/where they are/etc, including with the relevant plugins.

>because even if you do, the philosophy of vim is to keep optimizing your workflow, so you create a shortcut for shortcuts

That might be the philosophy of Emacs, but it's hardly the "philosophy of vim". In fact most old-time vim users I know try to keep their customizations to the minimum, so they feel at home to whatever system/vim they're thrown at.

Re:Technical Interview Performance by Editor, OS, and Language by splintercell on Wednesday September 20, 2017 @10:42PM (#15300214)
> Vim just takes longer for those tasks and gives worse overview/feedback on which they are/where they are/etc, including with the relevant plugins.

As I said, there are fast plugins for that task and slow plugins. Command-T and Ctrl-P are megafast because they are run as native binaries.

Re:Technical Interview Performance by Editor, OS, and Language by SAI_Peregrinus on Tuesday September 19, 2017 @04:21PM (#15288441)
Vim makes writing and editing text faster, that's true. But writing and editing text is a small portion of the time of a programmer. Planning what to write takes up far more time. I suppose it depends on language though: I tend towards low-level (VHDL, ASM, C) and so tend to need to think things out in more detail just to get working code. But even high-level programming should have plenty of planning, otherwise it tends to become bug-ridden very quickly. Worrying about the time spent editing text is premature optimization in the vast majority of cases.

I still like vim, I just don't think that argument is very convincing.

Re:Technical Interview Performance by Editor, OS, and Language by flukus on Tuesday September 19, 2017 @11:41PM (#15290632)
It may differ for you but coding is (sadly) not where the majority of my time is spent. A lot of it is in data files, logs, sql scripts, etc. For a lot of those tasks fast editing makes a big difference. Sql in particular is verbose and repetative yet fairly unstructured, a vim macro is a great way to do bulk updates. Another would be something like adding a parameter to a function called in many places, the repeat command is a fantastic way to apply it everywhere.
Re:Technical Interview Performance by Editor, OS, and Language by todd8 on Wednesday September 20, 2017 @03:21AM (#15291483)
I've touch typed for over 50 years, but I've never gotten really fast like some other software developers. However, this doesn't feel limiting, the thinking part is the limiting factor.

On the other hand, being really fluent in an editor (once upon a time in Vi, now Emacs) keeps me in a flow state. I think of code and it appears on the screen without interruption of the deep thoughts.

Re:Technical Interview Performance by Editor, OS, and Language by jnordwick on Tuesday September 19, 2017 @04:00PM (#15288270)
> in what other editors can you 'delete everything up to the next `=`

And how does being able to edit text a few seconds faster contribute to development speed and quality. Not a single bit. While it may let you feel cool, it really doesn't add anything to the bottom line.

Re:Technical Interview Performance by Editor, OS, and Language by ludston on Tuesday September 19, 2017 @11:27PM (#15290562)
Vim gives the ability to refactor large amounts of code rapidly. This doesn't make it so your typing speed is significantly faster, but it removes obstacles to refactoring large amounts of code which means that as a developer you will have more choices available to tackling some problems.

This can only really be shown via examples. Let's say, a lazy person has created a 3000 line file containing the declarations of a datastructure, and you would like to modify the constructors to each have an additional shared parameter.

In order to add this parameter you could add some behaviour to the constructor definition.

With vim you have a new choice open to you: you can define a macro that to find and modify all of the constructors in your declaration file in 20 seconds.

Now you can choose how you would like the constructors to look, rather than the choice being made for you by the existing code.

There are of course other ways to bulk-update text files, but the advantage of learning vim is that it is context-free. The same commands used to modify C# are fine to use for modifying javascript or XML. (i.e. you don't have to use parsing libraries)

Re:Technical Interview Performance by Editor, OS, and Language by coldtea on Wednesday September 20, 2017 @08:29AM (#15292948)
>Vim gives the ability to refactor large amounts of code rapidly.

It gives the ability to edit large amounts of code rapidly.

Refactoring implies design, coming with the right structure, applying some design pattern, etc -- which is the slow part, and not affected by your choice of editor.

If we're talking about "automated refactorings" (of the trivial variety, e.g. extract method, etc) then an IDE is an even better candidate than Vim.

>With vim you have a new choice open to you: you can define a macro that to find and modify all of the constructors in your declaration file in 20 seconds.

Or you know, I can do the same in any other editor with macros. Or use a regex, with almost all editors support and do it in 5 seconds.

Re:Technical Interview Performance by Editor, OS, and Language by ludston on Wednesday September 20, 2017 @09:40AM (#15293572)
I wrote a different reply to your post, but on replection you and I think vim is a different thing.

For me, vim is not my editor - It is a plugin that I install into all of my editors/ides (emacs, visual studio, etc.) so that the keybindings are familar and all of the normal tools (regex, macros, multiple clipboards) all work the same way.

Re:Technical Interview Performance by Editor, OS, and Language by ShabbosGoy on Tuesday September 19, 2017 @02:30PM (#15287453)
Or you could just use Spacemacs.
Re:Technical Interview Performance by Editor, OS, and Language by erikbye on Tuesday September 19, 2017 @03:35PM (#15288063)
Not sure why this got downvoted. While I prefer my own customized Emacs or Vim, Spacemacs is pretty decent from the jump. You just need to activate the layer for your language.
Re:Technical Interview Performance by Editor, OS, and Language by bfrog on Tuesday September 19, 2017 @05:11PM (#15288841)
This is what I've been doing and I have to say its pretty great.

There's always a few things that drive you crazy of course, but helm+projectile, flymake, and such are just so damn useful over using vim's poor attempts at the same.

Re:Technical Interview Performance by Editor, OS, and Language by komali2 on Tuesday September 19, 2017 @03:31PM (#15288037)
Dunno man, seems like I'd be missing ctrl+shift+f search across all files, with a nice little box that easily lets me filter out the .less files when I'm doing JS stuff, and vice-versa.

Obviously this is available in emacs, but not vim without serious configuring, and not with everything staying within a nice single editor context.

Re:Technical Interview Performance by Editor, OS, and Language by josteink on Tuesday September 19, 2017 @02:15PM (#15287290)
> Although, to be honest, using the GUI version of GNU Emacs as a Notepad replacement is possible: Just ignore the keyboard commands and interact solely via the menu up top. You even get access to at least some neat major modes this way.

Sure that's possible. And I realize that you're being hypothetical, but if that's how you're going to use Emacs, you're not going to see much gain in your productivity ;)

Re:Technical Interview Performance by Editor, OS, and Language by bitwize on Tuesday September 19, 2017 @03:40PM (#15288100)
Well, if you're gonna train a cat to walk on a leash, the first thing you do is drape a harness on its body, to get it used to the feel and smell of the thing before it walks anywhere.
Re:Technical Interview Performance by Editor, OS, and Language by pen2l on Tuesday September 19, 2017 @02:08PM (#15287206)
It does appear though that for on-site interviews, folks using emacs did not do well.

> Using Emacs and/or Vim is also a test of how much you care, primarily because they're not the default anymore

That's probably true, but I want to add that I used emacs/vim because I hung around with folks who looked down on other tools. So, it wasn't so much that I cared about my tools as it was about I wanted to fit in.

Re:Technical Interview Performance by Editor, OS, and Language by jcelerier on Tuesday September 19, 2017 @02:08PM (#15287201)
> Using Emacs and/or Vim is also a test of how much you care, primarily because they're not the default anymore, so anyone who uses them cares enough about their programming environment to use a non-default editor, and one which has a rather higher barrier to entry than most at that.

Depends, at the school I went to (less than five years ago), you start by learning emacs in the first month. A lot of people just stay with emacs for the remaining of the three years, because that's the first thing they learn.

Re:Technical Interview Performance by Editor, OS, and Language by pen2l on Tuesday September 19, 2017 @02:10PM (#15287230)
Oh wow, there are schools that introduce these tools?

I know that every SE degree includes a course on practices in which they go over version control, some diff tools, etc. but I wasn't aware of a school teaching vim/emacs. May I ask which school it is that is doing this?

Re:Technical Interview Performance by Editor, OS, and Language by deong on Tuesday September 19, 2017 @05:02PM (#15288771)
When I was an undergrad, we were "taught" tools like Emacs and Vim by being dropped into a systems programming class where we were told to telnet into a university server to complete the assignments, and "oh, you'll need an editor. I think Emacs and vi are there. You'll figure it out."
Re:Technical Interview Performance by Editor, OS, and Language by kccqzy on Wednesday September 20, 2017 @01:10AM (#15291000)
UCLA did, in its 35L class. You are required to do a series of text editing tasks and record keystrokes.

I should note that the professor, Paul Eggert, is the maintainer of many GNU projects.

Re:Technical Interview Performance by Editor, OS, and Language by CalChris on Tuesday September 19, 2017 @02:41PM (#15287571)
Berkeley 'taught' emacs in 61A when it used SICP and we programmed in Scheme, taught being in lower case here, italicized and in quotation marks. The idea that a university course would teach an editor is a bit much. I think there was a cheat sheet passed out by the TAs in section. My point is that this was at Berkeley where vi originated 40+ years ago.
Re:Technical Interview Performance by Editor, OS, and Language by josteink on Tuesday September 19, 2017 @02:17PM (#15287306)
At uni, that was what we were taught. On FreeBSD desktop-machines no less.

But that was 15 years ago. I have no idea what they teach now.

Re:Technical Interview Performance by Editor, OS, and Language by pswilson14 on Tuesday September 19, 2017 @02:18PM (#15287316)
Not OP, but UC San Diego taught both Vim and Emacs when I was there 5 years ago
Re:Technical Interview Performance by Editor, OS, and Language by jcelerier on Tuesday September 19, 2017 @02:42PM (#15287585)
ENSEIRB-MATMECA, a french engineering school
Re:Technical Interview Performance by Editor, OS, and Language by jhgb on Tuesday September 19, 2017 @02:58PM (#15287749)
> ENSEIRB-MATMECA

Are you sure that's actual French?

Re:Technical Interview Performance by Editor, OS, and Language by jcelerier on Tuesday September 19, 2017 @05:27PM (#15288974)
Re:Technical Interview Performance by Editor, OS, and Language by compumike on Tuesday September 19, 2017 @02:03PM (#15287155)
It's a reasonable hypothesis that there's probably a correlation with when someone started programming. Both editors and languages are "sticky" tool choices in that way.

FYI, I think there's a free version of PyCharm (Community Edition).

Re:Technical Interview Performance by Editor, OS, and Language by hashkb on Tuesday September 19, 2017 @02:20PM (#15287344)
I used TextMate and then Sublime for the first half of my 10 year career. It took seeing a coworker use vim to sell me on it, and within two weeks I was a better text editor than ever before.

You all know the rest of the story, but I'm one counterexample to the "how long have you been coding?" angle. I was meant to discover these editors even though I'm relatively young. (31 heh)

Re:Technical Interview Performance by Editor, OS, and Language by Osmium on Tuesday September 19, 2017 @03:13PM (#15287891)
> FYI, I think there's a free version of PyCharm (Community Edition).

I recently started using PyCharm CE over the last year and it really is a lovely IDE. I'm not surprised it works well in interviews, it makes it easy to get things done with minimum fuss.

Re:Technical Interview Performance by Editor, OS, and Language by rishabhparikh on Tuesday September 19, 2017 @04:47PM (#15288664)
Would also like to plug iPython Notebooks (Jupyter). Extremely useful for coding challenges/pair programming/ad-hoc testing!
Re:Technical Interview Performance by Editor, OS, and Language by buxtehude on Tuesday September 19, 2017 @02:56PM (#15287726)
Curious if Triplebyte interviews for all of dev/ops/devops positions?

Is there a higher/lower success rate in ops/devops vs pure development?

For example vim is used extensively in ops/devops and emacs use there is quite rare. If there is a higher success rate in ops/devops and if vim is used more in ops/devops - could this influence the results shown?

Fascinating data - thanks for sharing.

Re:Technical Interview Performance by Editor, OS, and Language by jtmarmon on Tuesday September 19, 2017 @03:31PM (#15288031)
And, indeed, eclipse is the editor most colleges use to teach undergrad students Java.