4 ms·
Not a programmer here, but would you say your productivity is impaired by boilerplate? I always got the impression the thing that ate up time was compiling, de
by sliverstorm 15y ago
Not a programmer here, but would you say your productivity is impaired by boilerplate?
I always got the impression the thing that ate up time was compiling, debugging and thinking. Not typing.
- wahnfrieden 15y agoThinking and debugging take up a lot of time, but typing time is still nontrivial and worth optimizing. Especially in debugging where moving around the file quickly is important, vim's movement commands make this quicker.
- conradev 15y agoI do agree that being able to navigate an editor like vim quickly is the determining factor in code writing, however, I do not think WPM is directly related to one's ability to do this. Even though I don't type insanely fast, I can hit a 1-5 key combination in an instant.
- FuzzyDunlop 15y agoCorrect me if I'm taking this the wrong way, but I don't think WPM even applies to programming. To audio typers, secretaries, etc. it's a good measure of how well you can keep up. To a programmer, you can only go so fast when you're not even dealing with human language that has no natural flow, and the quirks of the editor of your choice. Especially on, say, a Mac, where you could be typing a '#' far more times than you ever would in any other situation, or a backtick or pipe. It's probably telling that we're favouring languages that reduce the syntactic complexity of coding, like CoffeeScript in favour of Javascript, Ruby, maybe Python, Clojure, and the functional languages like Haskell and Erlang. Not just because it's easier to read, but because it's easier to type. I might just be talking rubbish, of course. But I wouldn't use typing speed as a performance metric for a programmer.
- jiggy2011 15y agoIt's not much of a performance metric , but I don't really enjoy typing very much in situations where I have decided what I'm going to do and then have to type it out. I can't generally think and type very well at the same time. This means for me that trying a random idea I have quickly is much more enjoyable in say python that it is in Java. Sometimes I want to just try something random in Java but I really can't be bothered to type all the code required to create a new class, handle exceptions and then also do the compile and run. If I had super fast typing skills or a more concise language I would find much less friction is doing that, this would make my programming time much more educational and make me better in the long run.
- ploversteno 15y agoIt's the fluency that steno lends to composing text or code that's far more useful than the speed. Tab-complete requires that you pause for a short time to read your options while you flip through them. Steno is entirely deterministic; you can implement the command in one stroke without twisting your hands around (unlike metacommands, especially those used in emacs, which can result in the dreaded emacs claw), and you know exactly what the result is going to be. Because you're writing entire words with each stroke, if you accidentally hit the wrong key, you'll be able to reverse the error in a single "delete last stroke" command, rather than having to backspace 20 times to correct a letter transposition error you made several words ago. Qwerty requires commands and variables to be broken down into minuscule portions, with the potential for error occurring each time a key is deployed. Steno reduces that error potential drastically by chunking words and variables into single-stroke entities, requiring less vigilance for error and allowing for a much smoother flow of thought and composition.
- a3_nm 15y agoTyping speed usually isn't the limiting factor, but being able to touch-type (really touch-type, which allows you to keep your eyes on the screen instead of going back and forth) is extremely valuable: it makes text entry much more natural, and allows you to catch typos.
- mattmanser 15y agoVisual Studio, for example, has boiler plate snippets, type prop[tab][tab] for a prop declaration, for[tab][tab] for a for loop, fore[tab][tab] for a foreach, etc. There's auto-brace completion and ctrl-enter to add a semi-colon and move to the next line (surprisingly useful with auto-braces). The point being that editors can make boiler plate very easy. To be completely honest these features don't save much time, even though I use them all the time. As you say thinking and debugging do, compiling not so much unless you're working on a very big project. Writing fast means you can express the idea in your head before you forget exactly how you figured it was going to work. This is the reason I find most compelling to be able to type fairly fast as well as know the keyboard shortcuts for jumping around (for example jump word in VS is ctrl-left/right arrow). Revelations can fade fast once you start implementing them.
- DennisP 15y agoCompiling is quick in many languages, but you're mostly right about debugging and thinking. However, the key to productivity is to stay in flow, and having to type the same boring boilerplate over and over again tends to take me out of it. http://en.wikipedia.org/wiki/Flow_(psychology) http://en.wikipedia.org/wiki/Flow_(psychology)