31–40 of 137 posts
Interesting talk. Naturally it made me think about steps I should take to prevent any kind of RSI. Should I be seriously concerned if I type for about 4-5 hours on average per day? How can I prevent it?
Basically review your work environment, keyboard, chair, table and posture.
Earlier quoted context omitted.
> you must work from home with that kind of setup. Or, you have a private office with a door that closes.
the day the average programmer gets an office, well... I don't even get a cube where I work
Earlier quoted context omitted.
the day the average programmer gets an office, well... I don't even get a cube where I work
Mentioned this on HN previously but as a nearly 40 year old developer who has been developing professionally for nearly 20 years -- it used to be the norm for programmers to get their own offices, even just the regular joe programmers... Places really tight for space might put two guys in a very spacious shared corner office... A few years into my career the idea of cubicles caught on and quickly became the norm, and…
You can largely thank Jim McCarthy of Microsoft fame for that, who in the mid 90s coined the concept, "beware of a guy in a room":
https://www.youtube.com/watch?v=oY6BCHqEbyc
https://blogs.msdn.com/b/david_gristwood/archive/2004/06/24/...
My counter-argument to voice-driven coding has been primarily around the input bandwidth and the fact that you must work from home with that kind of setup. I guess the presenter conducted the "faster than the keyboard" test under very controlled circumstances (e.g. only working on his own code, so one doesn't have to deal with non-english-word variables/functions). I don't mean to be a hater, because that was an _ama…
> you must work from home with that kind of setup. Or, you have a private office with a door that closes.
Sure, not the ideal, distraction-free environment, but neither is a cubicle farm.
I was trying to work something like this out to try about a month ago but had to put it aside for later. Running my speech recognition inside a virtual machine was a dealbreaker, but not all that uncommon for people doing this sort of thing. I really, really wanted to get Julius[1] running in OS X but after a couple tries I couldn't get it to build (problem on my end– this is a good reminder to get it sorted out). If…
I guess it depends on the type of software you're working on, but input speed has never been close to being the bottleneck with coding for me... Most of the time I'm trying to figure out what to do or how to implement an algorithm. Rarely do I get those mad-scientist frenzies where I'm typing away frantically trying to get all the words down as they come into my mind in a flash of inspiration.
It usually happens during refactoring, or when you're doing something you've done before, so you already know pretty much exactly what needs to be done and you're just executing. It also helps to stop coding for a minute, think what you want to do, then code until you stop typing for more than 5 seconds, repeat.
https://github.com/AshleyF/VimSpeak http://www.youtube.com/watch?v=TEBMlXRjhZY