r/coding • • Oct 04 '13

Just use Sublime Text (instead of vim)

http://delvarworld.github.io/blog/2013/03/16/just-use-sublime-text/
43 Upvotes

254 comments sorted by

View all comments

Show parent comments

1

u/nairebis Nov 25 '13 edited Nov 25 '13

source?

Just personal experience. I actually can't think of anyone I would tag as a "great coder" in my 30 years of experience who wasn't also a fast typist. Edit: To be fair, I'm sure there were a couple, but they weren't slow enough that I thought about it. And I've always been usually the fastest typist of the group, so it wasn't remarkable for someone to be a bit slower than I was.

But typing isn't anywhere near the top bottleneck for a coder's productivity.

If they're not typing most of the time, then I don't know what else they're doing. I mean sure, sometimes I need to go back and read the code to see what it's doing if I'm debugging, but otherwise I'm either typing in code or typing in debug code, or typing in commands to run the code, or something else that involves typing. But then, I'm also old school that my IDE is six Putty windows running Bash across two screens, and I rarely use debuggers (they are the slowest way to find bugs, but I won't try and prove that to you, if you're not already a believer. :) )

1

u/reasonably_plausible Nov 25 '13 edited Nov 25 '13

If they're not typing most of the time, then I don't know what else they're doing.

Have you never sat down to design the code that you are writing? Ever write formal specifications of what your code needs to do? Went to look up information on the specific domain you're programming in? Do you not have a test suite to run on your code? Depending on language, compiling?

EDIT: profiling use cases?

1

u/nairebis Nov 25 '13 edited Nov 25 '13

Have you never sat down to design the code that you are writing?

Yes, by typing. I generally type out structured notes and lists of questions to consider, then go through and grow that into a design. Generally, it's a lot of typing.

Ever write formal specifications of what your code needs to do?

Yes, by typing. How else? Unless you're talking about things like UML, which I consider a broken way to spec code. Diagrams are useful for database structures, though -- I will grant the latter is more diagramming than typing.

But API specs? If you're not typing a whole lot of words, then you're not creating good documentation.

Went to look up information on the specific domain you're programming in?

Sure, I will grant that's (usually) more reading than typing, but it's not more than 2-3% of the time.

Do you not have a test suite to run on your code?

Yes, which is programmed by typing it. Edit: If you're talking about running the test suite, then it's either a short enough time that it doesn't matter, or it's long enough that I switch away to work on something else.

Depending on language, compiling?

I have to admit that these days I do more dynamic languages than compiled languages, with the exception of Java (which is sort-of both), but compile times haven't been an issue in a long time. And back when they were, I would usually switch to some other window where I could be productive (by typing more code, of course).

1

u/reasonably_plausible Nov 26 '13

Generally, it's a lot of typing.

No thinking?

Yes, by typing. How else?

But is the typing the majority of the time that is taken up by this act? If you are commenting/documenting after the fact, it might be, but that is a bad habit and probably causing you to work harder than you have to.

Yes, which is programmed by typing it.

Running, reading, and interpreting the results and then finding where and what the problems are.

And back when they were, I would usually switch to some other window where I could be productive (by typing more code, of course).

This and switching during test code causes productivity drops due to context switching.

If you truly believe typing and editor speed to be a true bottleneck to coder productivity, how do you feel about pair programming (which in your view should decrease productivity by about 100%). But instead:

The results of the experiment indicate that it is feasible to develop software using distributed pair programming, and that the resulting software is comparable to software developed in collocated or virtual teams (without pair programming) in productivity and quality.

http://link.springer.com/chapter/10.1007/3-540-45672-4_20

on the more complex system, the pair programmers had a 48 percent increase in the proportion of correct solutions but no significant differences in the time taken to solve the tasks correctly

http://simula.no/research/se/publications/Arisholm.2006.2/simula_pdf_file

Results indicated that programming pairs performed at the level above the second best performers and at the level of the best performers in each nominal pair. This relationship was found to be consistent across both levels of task complexity.

http://aisel.aisnet.org/misq/vol33/iss1/7/