3 ms·
> It allows for minimal disruption to thinking process Willing to dive into this a bit more? My personal experience is different so I figure this is a chance t
by kelseyfrog 5y ago
> It allows for minimal disruption to thinking process
Willing to dive into this a bit more? My personal experience is different so I figure this is a chance to learn something new. The subjective character of typing experience for me is like riding a bike, driving a car, walking, or speaking. That is to say that unless I'm mountain biking, off-roading, on a balance beam, or trying to say a tongue twister, for the most part I'm unaware of the intention-execution-results loop, and the intention-results loop is all that consciously exists. My paltry 50-60wpm doesn't feel like an impediment to putting thoughts into text, but maybe others feel differently.
- throw10920 5y agoI frequently encounter typing speed as a disruption to my thinking process while developing my personal projects. My personal projects are developed interactively in the REPL - I'll make a few small changes to an existing piece of code, re-run it, and observe the difference in behavior before repeating. In this process, I usually conceptualize code significantly faster (2x-5x) faster than I'm able to type it, which translates to wasted time, where I know what code I want to write, but haven't written it. Now, from a philosophical point of view, I believe that it's possible to have programming tools that allow a 60wpm user to program at the speed of a 120wpm user without those tools (e.g. autocomplete allows you to type 10-character identifiers with significantly fewer keystrokes) - I just haven't finished building them. That is, I believe that having a slow typing speed shouldn't impede programmers, but does with our current tooling.
- Izkata 5y ago> My paltry 50-60wpm doesn't feel like an impediment to putting thoughts into text, but maybe others feel differently. That may be high enough that you don't have the impediment, but when you work with someone who types down around 10-15 WPM... You can definitely tell they're spending a lot of brainpower on hunt-and-peck instead of the problem they're actually trying to solve. Basically there's diminishing returns on increasing WPM and you may be at or past the tipping point. I expect it'll be different not just for different people, but also for whatever they're currently working on.
- usrbinbash 5y agoThe thing is, when a programmers starts to generate input, the problem is already solved, he is merely putting the solution into whatever representation the tools demand. I am not defending 10-15 WPM here ofc. just statingt that the majority of work happens before we start typing in code, and after we typed it.
- foxfluff 5y agoIt's a type-think-type-think cycle (or type-test-think-type-...) and the more time and effort you spend on the typing part, the more it distracts you from the rest. Typing for a few minutes isn't any better than compiling for a few minutes before you can test. It just interrupts the more interesting work.
- usrbinbash 5y ago> It's a type-think-type-think cycle Depends entirely on the individual developer. For me its think-think-think-think-drinkcoffee-think-type. And after the first iteration, the typing to make changes is usually miniscule compared to the initial amount.
- BlueTemplar 5y agoThat's due to unfamiliarity with the input device. And if they end up having to use it several hours per day, this slowness will go away in a few weeks.
- zepolen 5y agoThe easiest way to experience this is to remove 3 key caps from your keyboard eg. from T K and C. It will destroy your flow.
- foxfluff 5y agoFor me typing is the frustrating part, because when I know what I want the code to look like, having to type it in is just an annoying obstacle I have to go through before I can move on to the next thing, whether that's testing or thinking about the next bit of code or whatever. So yes, I do find it to be a distraction and frustration. Kinda like having to type a long random password and then dig out your phone and enter a 2FA code and then navigate a hierarchy of whatever before you can get to do the thing you're really after. I always wish I could type faster and with less effort, or -- better yet -- just wish the code into the shape I want. ~100wpm touchtypist here.