Live data from Hacker News

Typing Speed Test, but for Developers

haxxorwpm.0s.is

71–79 of 79 posts

Re: Typing Speed Test, but for Developers

#71
post #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.

I literally use vim. But if I can customize something system-wise instead of app-wise I'd always do that.

Re: Typing Speed Test, but for Developers

#72

Earlier quoted context omitted.

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

But the whole point was that it wasn't a separate role: it was a re-distribution of work so the developers were doing operations. Instead, a lot of people entirely missed the point and just renamed their ops people to devops.

Re: Typing Speed Test, but for Developers

#73
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

I don't understand why downvote something 100% factual and correct. Please explain!

Re: Typing Speed Test, but for Developers

#74
post #49

>grep -R "error" logs Why is error in quotes?

I found it reasonable because there's no need in this specific case but you do often use quotes and this could be a good middle ground of annoyance (line complexity) and getting the character distribution somewhat right

...but then you read the author's response about not having actually made this themselves and your head canon implodes

Re: Typing Speed Test, but for Developers

#75
post #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.

What does this have to do with Vim?

Re: Typing Speed Test, but for Developers

#76
post #18

The speed that I type is not related to the quality of my code. I think then type.

I'm honestly not even surprised by the number of comments saying how unimportant is the typing speed for a software developer. What a bunch of bullshit. What the heck you've been smoking, friends? Speed of reading and typing text it is absolutely the hallmark of a good programmer. Consuming and producing text is not only about code - code is nothing but structured text.

Software development is not purely technological discipline, we deal with socio-technological problems all the time. That means we need to consume and produce far more plain text rather than just code.

I mean sure, there are many facets to this and simply benchmarking and fretting about one's WPM won't magically make anyone a better programmer. But thinking it isn't important at all ain't right either.

Re: Typing Speed Test, but for Developers

#77
post #42

Typing speed only really matters for juniors and going into intermediate developers, after that point thinking methodology - abstraction design, data structures, system design, complexity isolation, matter way, WAY more. 50% because by the time you get to this your typing speed has crossed a threshold of no longer being the bottleneck and 50% because you are experienced enough not to make all the silly little mistake…

You mean to say programmers deal only with machines (and therefore code and shell commands) or something? Of course typing speed matters - we deal with Slack, Teams, emails, documentation, comments, LLM prompts, etc., daily. Sure no one's saying you must achieve stenographer's velocity or you can't call yourself a programmer. Still, typing speed has certain importance, it just can't be painfully slow, that's all. But thinking it doesn't matter at all is a manner of hubris.

Re: Typing Speed Test, but for Developers

#78
post #51

Earlier quoted context omitted.

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…

ifconfig is still the standard on *BSD, MacOS and other Unixen. Plus its output is more readable on Linux than ip IMO, because it adds a blank line between interfaces.
Post reply on HN