3 ms·
Not to mention the "I'm writing this code to hack this system before the guy wakes up, but I should still comment it! Someone may have to maintain it." part.
by StavrosK 12y ago
Not to mention the "I'm writing this code to hack this system before the guy wakes up, but I should still comment it! Someone may have to maintain it." part.
- kaolinite 12y agoFor what it's worth, if I'm writing a quick script I'll often write a few quick comments first (e.g. "Load data from file", "Connect to API", etc) before I start writing any code, just to plan it out. Similar to how many people will create a bunch of empty methods when creating a new class, before fleshing them out.
- StavrosK 12y agoIf I remember correctly, he was hacker-typing it as he went, top to bottom, which was a bit funny.
- DennisP 12y agoMovies should get vim or emacs experts to type their code, it'd be a lot more impressive.
- StavrosK 12y agoEh, we still type at an average speed in insert mode :-P
- DennisP 12y agoIf you're staying in insert mode you don't qualify as a vim expert. Rapid-fire editing with text objects, dot, macros, column mode, :norm, and so on ought to work pretty well on screen.
- StavrosK 12y agoYeah, not when you're typing a stream of code.
- DennisP 12y agoWell obviously that's not what I'm proposing to show.
- moe 12y agoRapid-fire editing with text objects [...] ought to work pretty well on screen. I wish they'd just do away with the rapid-fire crap altogether. It breaks the immersion. A mildly witty easter egg does not compensate for making every nerd in the audience of your nerd-movie cringe... Just show some realistic typing, with mistakes and perhaps a quick copy/paste.
- DennisP 12y agoI'm not saying anything extreme, just something realistic for an accomplished vimmer, which is impressive enough and would do the opposite of making nerds cringe.