Red Rozenglass on Nostr: Ignas Kiela Normal Mikoto :kagami_shrug: :gekota: Wolf480pl I hear the idea of ...
Ignas Kiela (nprofile…3wfk) Normal Mikoto :kagami_shrug: :gekota: (nprofile…nc0q) Wolf480pl (nprofile…6yr6) I hear the idea of bottlenecks discussed in regards to typing, but it doesn't make sense to me. It doesn't apply when things are of different nature; i.e. thinking and typing. You think about bottlenecks in something uniform, like code, to know where to focus your efforts for performance improvement. But when discussing typing and thinking, you don't really reallocate your focus from improved typing speed to improved thinking speed instead.
For example: if we estimate, in an average code base you work on, you type for 25% of time, and think for 75% of time, and you worked on the project for 4 hours per-work-day, for a month, that's 22 days * 4 hours = 88 work hours, of which 22 hours are typing. If you double your typing speed, you would save 11 hours per-month, which is 132 hours per-year.
So, even if you invest 100 hours to improve your typing speed, you would break even in less than a year, and then, you'd have 132 extra hours of free time every year from then onward. Plus, the street cred among peers, and you have less chance of typing taking a bit too long and breaking your thought chain, and good typing posture reduces risk of hand injury, etc. etc.
So, I'd say, it does matter. If you can, by allocating a similar amount of time, improve your thinking speed by around 16%, then yup, that would be a better allocation. But there are limits to that, and once you reach the limits of speed improvement for your thinking, your next best bet is improve typing speed.
But who am I kidding, for most working dev people, the thing that would provide most productivity improvement is to get rid of most meetings, and most incompetent managers, thought and typing speeds pale in comparison to those time sinks.
Type on friendos :3
For example: if we estimate, in an average code base you work on, you type for 25% of time, and think for 75% of time, and you worked on the project for 4 hours per-work-day, for a month, that's 22 days * 4 hours = 88 work hours, of which 22 hours are typing. If you double your typing speed, you would save 11 hours per-month, which is 132 hours per-year.
So, even if you invest 100 hours to improve your typing speed, you would break even in less than a year, and then, you'd have 132 extra hours of free time every year from then onward. Plus, the street cred among peers, and you have less chance of typing taking a bit too long and breaking your thought chain, and good typing posture reduces risk of hand injury, etc. etc.
So, I'd say, it does matter. If you can, by allocating a similar amount of time, improve your thinking speed by around 16%, then yup, that would be a better allocation. But there are limits to that, and once you reach the limits of speed improvement for your thinking, your next best bet is improve typing speed.
But who am I kidding, for most working dev people, the thing that would provide most productivity improvement is to get rid of most meetings, and most incompetent managers, thought and typing speeds pale in comparison to those time sinks.
Type on friendos :3