Nice UI! For programmers trying to improve their general typing speed I reckon it could help, but for me it creates an almost uncanny experience. In the JS test I found it incredibly difficult to type out `/^(?:parents|prev(?:Until|All))/`, because my mind interprets it somewhat like its AST -- i.e. I see a delimited regular expression with an uncaptured group nested within another uncaptured group. I focus on the op…
Typing.io: Typing Practice for Programmers
61–70 of 79 posts
Re: Typing.io: Typing Practice for Programmers
#62Re: Typing.io: Typing Practice for Programmers
#63This is an example of a product I would buy, but would never buy as subscription software. $60/year to infinity is about $600 at a 10% discount rate. Sorry, but it's probably worth about $25 to me, not $600.
Re: Typing.io: Typing Practice for Programmers
#64Earlier quoted context omitted.
Your disagreement is kind of out of place here; no claim was made of where the productivity boost of autocomplete ranks against other development factors. Besides, whether or not you use autocomplete is orthogonal to your framework choice.
* no claim was made of where the productivity boost of autocomplete ranks against other development factors No, but it can be inferred. I agree that code completion and framework choice can be mutually exclusive; my general point is that a developer's decision to use a tool should consider other productivity factors, not just the expected ones.
I don't think so. We ought to be able to describe our own experiences without making a claim about productivity in general. It seems clear to me that peeters was doing exactly this, and not implying that his experience ought to be indicative of others.
Re: Typing.io: Typing Practice for Programmers
#65Earlier quoted context omitted.
Your disagreement is kind of out of place here; no claim was made of where the productivity boost of autocomplete ranks against other development factors. Besides, whether or not you use autocomplete is orthogonal to your framework choice.
* no claim was made of where the productivity boost of autocomplete ranks against other development factors No, but it can be inferred. I agree that code completion and framework choice can be mutually exclusive; my general point is that a developer's decision to use a tool should consider other productivity factors, not just the expected ones.
Re: Typing.io: Typing Practice for Programmers
#66This tool is perfect. - I'll recommend to you that you're marketing it all wrong. - I'd make this into a tech-interview/learn a new language site. Before I crack any book for any language, I download gists of the code and start typing it out. Imagine, python/c the hard way in this? What is a namespace? What is an import? Inline explanations of what you're doing would go a long way. Dare I say it, this could be the fi…
Spot on. This would be great as a way to learn new frameworks/libraries as well.
Additionally, in the process of mimicking code, the only thing I could do was think about what I was writing - and in some cases I discovered that I would have done it differently than some of the libraries I use every day.
Re: Typing.io: Typing Practice for Programmers
#67Although typing certainly isn't a big development bottleneck, being able to type fast lowers your overall cognitive load and lets you stay in the problem domain you're working on.
It's not like loud noises are a programming bottleneck either -- but it's certainly nice to eliminate a nuisance.
Re: Typing.io: Typing Practice for Programmers
#68Learning to type quickly is a valuable skill. But with programming, is typing speed a common bottleneck? It seems akin to learning how to turn a steering wheel more quickly or how to hammer faster.
Re: Typing.io: Typing Practice for Programmers
#69Re: Typing.io: Typing Practice for Programmers
#70All this does is make me realize how much I take my IDE for granted. In no example that I tried did I even get past the first line before I missed using IDE autocomplete or shortcuts. It got under my skin that I had to type out each character. Take the Scala example. I would NEVER type "@SerialVersionUID" with correct casing. I'd maybe type "@Ser" and then auto complete. Or "@SV" and then auto complete. I can't recal…
I have to somewhat disagree, I think autocomplete is one of those IDE features that is no doubt quite useful but I think its contribution to developer productivity is greatly exaggerated... frameworks that are well designed for instance are far more important contributors to developer productivity... so my question to you is, what if a tool has a framework that allows you to get a lot done with significantly less cod…