The leaderboard angle is smart too,people love competing on pointless metrics and wpm is the perfect one for that.would love to see a mode for specific tools tho, like a docker-only round or a vim escape sequence speedrun. The git rebase one would genuinely stress test people lol.
Typing Speed Test, but for Developers
11–20 of 79 posts
Re: Typing Speed Test, but for Developers
#12Something 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…
Re: Typing Speed Test, but for Developers
#1360s | Basics category | 79 wpm | 100% acc | 38 cmds | QWERTY | Logitech K200 (membrane keyboard from like 2007)
Fun idea, I like the categories and the option to specify keyboard+layout in the highscore, and the page layout/design is very clear. Thanks for making!
Re: Typing Speed Test, but for Developers
#14Re: Typing Speed Test, but for Developers
#15Something 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 seeing a lot of people that having that train of thought. I think that is a fallacy. I can understand that some LLM execution can be faster, but definitely not all. Agents need to explore, grep and get back up to speed to get context, if you have a good mental model, you can do changes or adaptions in One could argue to find the Therefore I’m thinking one task that can be done in one context window without switch…
A lot of times human commands are prone to errors / edge cases as well. Example a simple git pull command usually would take A simple git push is usually instant but that comes with an overload of some un intended changes being pushed, which LLMs take care of removing themselves.
When LLM is doing its thing, we can spend the same time in writing the next prompt.
Re: Typing Speed Test, but for Developers
#16This is fun lol. typing tests but for terminal commands instead of regular words is such a niche idea but it actually makes sense. every dev has typed git pull origin main so many times their fingers do it on autopilot, so measuring that muscle memory is a cool way to track terminal fluency. The leaderboard angle is smart too,people love competing on pointless metrics and wpm is the perfect one for that.would love to…
Re: Typing Speed Test, but for Developers
#17; 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 & o::SendText "_"
CapsLock & p::SendText "+"
CapsLock & m::SendText "-"
CapsLock & e::SendText "="
Re: Typing Speed Test, but for Developers
#18Re: Typing Speed Test, but for Developers
#19The speed that I type is not related to the quality of my code. I think then type.
Re: Typing Speed Test, but for Developers
#20This seems to be largely devops stuff, not developer. (Or plain ops.)