thanks, it also does not look fast to me and does not seem to improve the process the way it does for speech. Additionally I guess there is a steep learning curve so it is definitely not for everybody
considering typing time isn't even close to the most time consuming part of programming, I don't think this will be relevant to programmers apart from the programmers who want to do it for fun
While nobody can deny the fact that most of the time in programming indeed is not spent writing, how about this: you type slower than you can think.
So, when you get an idea, it's nice to be able to transfer the idea to the source code, so you can then move on the next idea or next part of the same one. You don't want to be held back by an inferior input method or a language with a lot of ceremonial about doing simple stuff. This happens in short bursts, even if the total time is quite short.
Sometime it happens so that one thinks faster than one can speak. This usually leads you to get mixed up in words.
A fast way to enter ideas is an important part of developing ergnomics.
Docstrings, writing documentation, talking to colleagues on Slack, asking questions on stackoverflow, writing mails, browsing, working in the terminal. We spend a lot of time writing. How much time could one save by e.g. doubling the speed?
Another aspect is of the working memory - will it free your brain's resources? Will allow writing at the speed of thought allow for new/more thoughts?
I think we should explore these waters, and steno is a solid choice.
keyle|4 years ago
So with typing keywords fast and efficient auto-completion, I doubt Steno would somehow make you a faster developer.
Clarity and correctness rules over speed here.
kremlin|4 years ago
_flux|4 years ago
While nobody can deny the fact that most of the time in programming indeed is not spent writing, how about this: you type slower than you can think.
So, when you get an idea, it's nice to be able to transfer the idea to the source code, so you can then move on the next idea or next part of the same one. You don't want to be held back by an inferior input method or a language with a lot of ceremonial about doing simple stuff. This happens in short bursts, even if the total time is quite short.
Sometime it happens so that one thinks faster than one can speak. This usually leads you to get mixed up in words.
A fast way to enter ideas is an important part of developing ergnomics.
comma_at|4 years ago
Docstrings, writing documentation, talking to colleagues on Slack, asking questions on stackoverflow, writing mails, browsing, working in the terminal. We spend a lot of time writing. How much time could one save by e.g. doubling the speed?
Another aspect is of the working memory - will it free your brain's resources? Will allow writing at the speed of thought allow for new/more thoughts?
I think we should explore these waters, and steno is a solid choice.