I think it's a neat idea, but I don't think I personally would use it much - a lot of how I think and organize code is visual. For example, I'll write half of a

I think it's a neat idea, but I don't think I personally would use it much - a lot of how I think and organize code is visual. For example, I'll write half of an invocation of a function, move it around a bit, and then complete the signature. Or I'll write out something three ways, jiggle them around a bit, combine two, and erase the third, and then move the block back to where it actually belongs. It's similar to math - when I was in university, I broke several bones in my writing hand about two months before I had a calculus exam. I knew I wouldn't be able to write for my finals, and I spoke to the Disability office to make a reservation for someone to write for me. So I decided to hire a guy for a few weeks to get comfortable with doing math verbally, like I would have to do for the final. After about a week I decided it was pretty hopeless - my whole workflow was gone, I couldn't sketch out ideas since there was such a mental load in "writing down" haldf an idea, etc. As a result, I just learned to write semi-legibly with my off hand, and had the guy whose job it was to transcribe my math recopy what I scribbled with my left into something readable. Moral of the story, at least for how I work, is that you should have very good support for moving text around.