Live data from Hacker News

Typing Speed Test, but for Developers

haxxorwpm.0s.is

61–70 of 79 posts

Re: Typing Speed Test, but for Developers

#61

Only slightly related, but what increased my code typing speed the most is this (AutoHotKey 2): ; CapsLock + J/K -> ( ) CapsLock & j::SendText "(" CapsLock & k::SendText ")" ; CapsLock + U/I -> [ ] CapsLock & u::SendText "[" CapsLock & i::SendText "]" ; CapsLock + L/: -> { } CapsLock & l::SendText "{" ; SC027 = physical ;/: key on a US keyboard CapsLock & SC027::SendText "}" ; CapsLock + O/P/M/E -> _ + - = CapsLock &…

Dude, just use vim.

Re: Typing Speed Test, but for Developers

#62
I believe the real test would be if this accounted for (at least) people's aliases, and perhaps functions. So parse their .bashrc, .zshrc, .profile, etc. and expand the commands using those aliases to see if the eventual command executed matches the one that is expected here.

Re: Typing Speed Test, but for Developers

#63
post #8

This seems to be largely devops stuff, not developer. (Or plain ops.)

It used to be that DevOps was the movement of merging Ops leftwards so that Devs own the Operation of their software.

THANK you![1]

Calling anything ops "DevOps" is right up there with calling JSON APIs "REST."

I know it's silly to let it bother me, but man does it get under my skin.

1. https://imgur.com/gallery/thank-you-lNUh0uV

Re: Typing Speed Test, but for Developers

#64
post #51
post #21

There is no autocompletion, that's not realist. I never type "apt-get install nginx" I type "apt-g ins ngi "

apt-get is kinda old, "apt" is the new thing. It unifies some commands like apt-get, apt-cache, and probably something else but those are the only 2 I use :D

apt-get / apt-cache is one of those things that I simply cannot get out of my muscle memory. It's probably an alias under the hood by now, but I hope they never get rid of it.

Ofc stuff that is actually deprecated is a different story.

When I see some kind of tutorial or whatever from 2025 by a young dev and he is using ifconfig instead of ip or similar stuff... I am having a hard time holding myself back not telling them ifconfig was deprecated before they were even born :)

On the other hand sometimes when my brain goes full autopilot it still defaults to writing

/etc/init.d/someservice restart

Like sysV wasnt out for a decade by now

Re: Typing Speed Test, but for Developers

#67

Earlier quoted context omitted.

It used to be that DevOps was the movement of merging Ops leftwards so that Devs own the Operation of their software.

THANK you![1] Calling anything ops "DevOps" is right up there with calling JSON APIs "REST." I know it's silly to let it bother me, but man does it get under my skin. 1. https://imgur.com/gallery/thank-you-lNUh0uV

it’s a meaningless term that can define dozens of roles

Re: Typing Speed Test, but for Developers

#68
post #31

Something I realized with the new LLM tools is that learning how to type plain English words fast i.e. without capitalization or punctuation, and even typos is not that big of a problem anymore. And so it follows that code-specific typing is even less important if you can just type in normal words fast and then just check it's output. Although yes for stuff this small i.e. super small terminal commands I feel there d…

I'm not sure. And to be honest, typing speed was never that big a deal. By the time I got out of college a few decades ago I was in the 110-120wpm range. However as I progressed in my career as a developer what I found is that both my "working" WPM and then my "normal" WPM dropped over time. Once I moved out of truly junior, pure code grinding roles, I spent more and more time thinking, talking to people, etc than I…

To an extent, but not to that extent.

There's a significant difference between (say) 20wpm and 100wpm. -- Your comment is 150-200 words; so that's the difference between spending two or three minutes vs ten (just typing it out, not counting the time it takes to think).

If you limited your typing throughput to 10wpm, how long of a comment are you really going to reply with? Probably not a long one. -- If someone types at 160 wpm, are they going to type a better comment than someone typing at 80 wpm? Maybe? Maybe not? Probably not twice as long / twice as good.

I still think "typing speed is about latency, not throughput" is the key perspective. (Followed by diminishing returns. I think around 80wpm is fine). -- There are some cases where I'm doing the activity so infrequently that the cost of improving outweighs any benefit I'll see.

Re: Typing Speed Test, but for Developers

#69
post #31

Earlier quoted context omitted.

I'm not sure. And to be honest, typing speed was never that big a deal. By the time I got out of college a few decades ago I was in the 110-120wpm range. However as I progressed in my career as a developer what I found is that both my "working" WPM and then my "normal" WPM dropped over time. Once I moved out of truly junior, pure code grinding roles, I spent more and more time thinking, talking to people, etc than I…

To an extent, but not to that extent. There's a significant difference between (say) 20wpm and 100wpm. -- Your comment is 150-200 words; so that's the difference between spending two or three minutes vs ten (just typing it out, not counting the time it takes to think). If you limited your typing throughput to 10wpm, how long of a comment are you really going to reply with? Probably not a long one. -- If someone types…

There is a thing about getting to 120 though. Like, being able to connect at that speed with everything working perfectly in sync.

Re: Typing Speed Test, but for Developers

#70

Earlier quoted context omitted.

To an extent, but not to that extent. There's a significant difference between (say) 20wpm and 100wpm. -- Your comment is 150-200 words; so that's the difference between spending two or three minutes vs ten (just typing it out, not counting the time it takes to think). If you limited your typing throughput to 10wpm, how long of a comment are you really going to reply with? Probably not a long one. -- If someone types…

There is a thing about getting to 120 though. Like, being able to connect at that speed with everything working perfectly in sync.

As the GP, I've been there. And my point was that it really hasn't been useful in my career. To the extent that my wpm has dropped over time.
Post reply on HN