An Empirical Study of Programmers’ Acquisition of New Programming Languages [pdf]
&gt; “Given the positive sentiments towards in-line compiler errors and the lowered work-flow overhead resulting from removing the requirement of compiling within the shell, we recommend language developers create packages to make compiler mes- sages accessible in-line. This is consistent with prior work suggesting that the location of error messages and their struc- ture is critical [8].”<p>Ugh, this type of result is so depressing to me. I am a “young” developer (early thirties, most experience with modern C, Python and Haskell).<p>I just want to work in the shell! Stop foisting shitty UI tools on me to code with. They are not good. <i>They just aren’t.</i><p>I just want a shell, non-window mode Emacs, and command line search tools. My workflow is read read read type type type ctrl-z from Emacs to the shell run run run fg 1 back to Emacs. Always use git grep and ag to find code, never ever use “jump to definition” features not even in huge codebases (it’s just too slow mentally to rely on that context switch instead of ctrl-z git grep ... emacs -nw ...).<p>The absolute most I’ll tolerate is syntax highlighting.<p>The idea of compiler errors popping up in my editor with little Xs or squiggly underlines like a MS Word doc makes me throw up a little in my mouth. Gross.<p>Every single time I’ve invested effort to become a proficient user of these types of tools, like intellij stuff and sublime and VS Code, it just kills productivity and I go right back to Emacs + shell programs.