11–20 of 78 posts
However I could see myself using voice commands that activate Macros or other actions. I just bought a Nexus9 and am going to try to use it for coding, I can definitely see potentially using voice commands to augment that workflow.
Earlier quoted context omitted.
A "rubber dome" or membrane keyboard requires the typer to press the dome all the way down to trigger the key press. On a mechanical keyboard, it is a mechanical switch to trigger the keypress. On Cherry MX blacks greens and reds, there is no feedback when you have pressed the key. However on a blue or a brown there is a tactile "bump" when the press is registered. Critically this happens before the key "bottoms out"…
MX blue and brown keys also require slightly less force to press than a rubber dome key.
Red (45 centiNewtons, 60 cN)
Brown (45 cN, 60cN, tactile)
Blue (50 cN, 65 cN, click/tactile)
Black (60 cN, 80 cN)
Clear (65 cN, ?)
Green (80 cN, 105 cN, tactile)
Has anyone tried to add gestures, with a Leap Motion for example, to their development process? A handful of subtle motions could be used to automate some repetitive tasks.
Leap Motion isn't nearly as accurate as they show in their videos. I have one and it's completely useless for anything more than a simple "swipe left" gesture.
However, I've started to experiment with combining the leap with a mouse--i.e. left-hand over the leap and right-hand on the mouse--to control a single hand grabber/toucher/pointer object. I assign broad movements to the mouse and much finer movements to the Leap. It seems to work well, in much the way that arms work for large motor control and wrists work for fine motor control.
This was a pretty interesting read. One thing I can recommend for those with RSI are Cherry MX Blue switch keyboards. As someone with fairly severe RSI, making the change from my normal rubber-dome keyboard over to the Blue Cherry MX switches about 2 years ago has made things significantly better. The pain and discomfort is largely gone-- its still there, of course, but its hardly noticeable.
this is all I think of when I think about programming by voice: https://www.youtube.com/watch?v=KyLqUf4cdwc I remember laughing so hard the first time I saw this. (granted its from vista, and I know voice has come a long way since then) However I could see myself using voice commands that activate Macros or other actions. I just bought a Nexus9 and am going to try to use it for coding, I can definitely see potentiall…
In the interval, I switched to a standing desk and it did _amazing_ things for my hands. I tend to slouch when sitting, and just standing while I worked for several periods a day reduced the pain a lot.
I'm currently trying to solve my RSI problems by going farther than the normal progression of ergonomic peripherals. If that doesn't work, I'll have to give up and go to voice control. I've designed and built my own chording keyboard, which should be 10x less stressful to type on than a normal keyboard. I also have an eye tracker that I'm going to program to use to replace most mouse tasks. I don't like the idea of i…
This was a pretty interesting read. One thing I can recommend for those with RSI are Cherry MX Blue switch keyboards. As someone with fairly severe RSI, making the change from my normal rubber-dome keyboard over to the Blue Cherry MX switches about 2 years ago has made things significantly better. The pain and discomfort is largely gone-- its still there, of course, but its hardly noticeable.
I find rotating between different types of input devices helps the most. Some weeks, I work on a laptop. Some, at a PC with a common mouse and keyboard. Some, with my Unicom and a trackball. I also change up how I sit, and the location of monitors. Any one system eventually leads to the same pain.
Personally, I'd opt for Dasher: http://www.inference.phy.cam.ac.uk/dasher/