• 0

Programmers, what's your typing speed?


Question

Recommended Posts

  • 0

I can definitely relate to that. I am a fast typer when I want to, but it's just a hell of a lot of effort to keep up. I tend to type pretty quickly when just writing prose, but deliberately slow down when coding. Mainly because it gives me time to think about what code I'm writing whilst I'm writing it and what I'll do next which I find useful. Another upside is that when I slow down when coding I barely make any mistakes at all, even with weird character combinations, whereas I do a lot more when going full speed and end up wasting time deleting and redoing.

  • 0

Very, very low. But that is down to the fact that I'm most of the times reading documentation and trying to make something work. If I know what I am doing, then it is fast enough, I'd say, especially since Visual Studio helps a lot with everything nowadays when it comes to writing the actual code.

  • 0

Yea it depends on what I'm typing too.. if I'm doing plain text like typing an email, documentation or whatever, I usually do around 95 WPM or so accurately, can go faster but then I tend to start making mistakes. But it's probably a fair assumption that most people will drop significantly in speed while coding due to special characters, thinking about what they're doing, switching tasks, etc etc, never mind most IDEs will do a lot of the typing for you to begin with like with Intellisense, code completion/refactoring and whatnot and that makes it hard to gauge speed too.

  • 0
  On 11/05/2015 at 16:16, Max Norris said:

Yea it depends on what I'm typing too.. if I'm doing plain text like typing an email, documentation or whatever, I usually do around 95 WPM or so accurately, can go faster but then I tend to start making mistakes. But it's probably a fair assumption that most people will drop significantly in speed while coding due to special characters, thinking about what they're doing, switching tasks, etc etc, never mind most IDEs will do a lot of the typing for you to begin with like with Intellisense, code completion/refactoring and whatnot and that makes it hard to gauge speed too.

Same, like I don't know exactly how fast I type, definitely not the fastest.  It depends on how much thinking I have to do with my writing.  I mean, I can write without looking at the keyboard but the longer the words.. the longer it takes me to write it.  I still only really type with one finger on each hand I can't do the multi finger typing... but I can do it without looking.

  • 0

1 -3 words per minute. That was the result from some online typing test my wife made me take.

 

I'd say it was wrong, but then who'd believe me?

 

In reality, I'm not sure how important typing speed is when programming. Very rarely am I just "hammering out code". Usually most of my time and effort is in mentally securing what I'm doing (either researching the code base, reading documentation, or figuring out how I'm going to code something)... The actual code typing doesn't usually take long at all.

  • Like 2
  • 0

About 80 wpm when I'm taking a typing test and really try hard. But as others mentioned, you don't need high typing speed to be a good programmer. If anything low typing speed might push you towards more minimal and succint code that is simpler to understand.

 

  On 11/05/2015 at 16:25, LogicalApex said:

1 -3 words per minute. That was the result from some online typing test my wife made me take.

 

I'd say it was wrong, but then who'd believe me?

If that's true, then it just took you between 30 and 90 minutes to write that post. I find that quite hard to believe :|

Are you sure it's not 1-3 words per second?

  • Like 2
  • 0
  On 11/05/2015 at 19:33, Andre S. said:

If that's true, then it just took you between 30 and 90 minutes to write that post. I find that quite hard to believe :|

Are you sure it's not 1-3 words per second?

I write at 1-3 words per minute.  This post took me 9 minutes to write

  • Like 2
  • 0
  On 11/05/2015 at 20:07, tsupersonic said:

I can type 100-110 wpm, but not when I'm programming. I usually have to take the time to think through the code.

 

yeah, coding wpm, and dictation is obviously different speed.

  • 0

I feel your pain. I try to pace myself but when I'm working on something that I simply have lots of code to write (ie prototyping something or writing boilerplate code) I too tend to go too fast to the point of exhaustion. I am not as good at taking breaks either so my wrists ache like hell...

  • 0

I've never been a fast typist, my kids razz me and tell me that for someone who has been using computers as long as I have, I should type much faster.  I always tell them that I don't get paid to type fast, I get paid for knowing what to type.

  • 0

I type English at roughly 75-85 WPM with a decent level of accuracy.

 

I program significantly slower. There is no real measurable speed since typing isn't what takes time, it's thinking about what to type. Maybe 30-80 Lines an hour? Not sure.

  • 0

On the pain aspect, OP have you considered buying some tennis balls and making a tiny puncture into them?

Stay with me

 

It helps me when I write (lately I get all sorts of pain and cramps when handwriting, and have found that maybe 15-30 minutes of squeezing a punctured tennis ball helps, (good stress relief too, as you can still throw it)

  • 0
  On 11/05/2015 at 20:07, tsupersonic said:

I can type 100-110 wpm, but not when I'm programming. I usually have to take the time to think through the code.

 

I agree. At peek, I can hit 130wpm, but not when coding. Too much thinking to do for that kind of speed.  I figure I probably pull about half that when coding, and less if debugging.

This topic is now closed to further replies.
  • Posts

    • Microsoft reportedly planning to lay off thousands of employees, mostly in sales by Usama Jawad Back in May 2025, Microsoft decided to lay off 3% of its workforce, which amounted to roughly 6,000 employees. It claimed that this decision allowed it to implement better organizational changes in a "dynamic marketplace". Now, a new report claims that the Redmond tech firm is planning to lay off thousands more next month. Citing unnamed sources, Bloomberg reports that as the company continues investing heavily in its AI ventures, it is about to announce layoffs of thousands of workers as early as next month. This reduction in workforce will primarily affect sales teams, but they won't be the only ones affected. That said, the sources did mention that the timing for this announcement may change. This move, if true, won't be entirely surprising. In April 2025, Microsoft announced that it will be relying more on third-party firms to sell its software to small- and medium-sized customers. It's currently unclear how many employees will be impacted by this change, but even if the layoff percentage is in the single digits, it would still be significant as it would be impacting the professional careers of thousands. The May 2025 layoffs primarily impacted engineering and product teams. The other major round of layoffs prior to this was the decision to eliminate 10,000 jobs back in January 2023. Those represented 5% of the total workforce at that time, with numerous teams, including the one leading Mixed Reality (MR) efforts, being heavily impacted. It is interesting to note that if the timing of the announcement for layoffs is accurate, it would be soon after Microsoft closes its fiscal year at the end of June 2025. Although we'll get financial reports for the latest quarter soon after too, one has to wonder what the human cost of profit is, as Microsoft continues to report billions of dollars in revenue every quarter. Source: Bloomberg (paywall)
    • Ah .. lockout for suspicious activity. I bet they uploaded the SanDisk utility detected as malware
    • Microsoft 365 will soon disable outdated authentication protocols for file access by Usama Jawad On a fairly regular basis, Microsoft disables outdated protocols that are used to access its services. In the past few years, the company has deprecated Basic Auth in Exchange Online and cut access to Outlook for third-party apps relying on this protocol. Now, it has decided to get rid of old authentication protocols for file access across Microsoft 365 services. As reported by Bleeping Computer, Microsoft has posted a message on its Microsoft 365 Admin Center. Starting from mid-July 2025, the company will begin disabling legacy authentication protocols used to access files across Microsoft 365 and Office apps, SharePoint, and OneDrive. Essentially, applications or services which use the Relying Party Suite (RPS) or FrontPage Remote Procedure Call (FPRPC) will to perform browser-based authentication to perform open operations on Office files will no longer be able to do so. As expected, this is primarily being done to improve the cybersecurity posture of various services. Microsoft states that RPS can be brute-forced and phished with relative ease as it is fairly outdated. Similarly, FPRPC is typically used for remote web page authoring and it is susceptible to exploitation through various vulnerabilities too. As such, both of these protocols will be disabled by default starting from mid-July 2025, with the rollout of this change targeting completion by August 2025. The Redmond tech giant will update the protocol baseline by default without mandating any licensing changes for customers. In addition, once these modifications are rolled out, Microsoft 365 will require admin consent to get third-party access to files and sites. IT admins can view the guidance available here to configure admin consent workflows. Microsoft says that these changes align with the principles of its Secure Future Initiative (SFI). Earlier today, it announced the rollout of improved security defaults for Windows 365 citing the same reasons too.
    • This is how you kill your own business.
  • Recent Achievements

    • First Post
      Fuzz_c earned a badge
      First Post
    • First Post
      TIGOSS earned a badge
      First Post
    • Week One Done
      slackerzz earned a badge
      Week One Done
    • Week One Done
      vivetool earned a badge
      Week One Done
    • Reacting Well
      pnajbar earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      705
    2. 2
      ATLien_0
      283
    3. 3
      Michael Scrip
      216
    4. 4
      +FloatingFatMan
      194
    5. 5
      Steven P.
      130
  • Tell a friend

    Love Neowin? Tell a friend!