Live data from Hacker News

Typing.io: Typing Practice for Programmers

typing.io

51–60 of 79 posts

Re: Typing.io: Typing Practice for Programmers

#51
post #31

Earlier quoted context omitted.

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…

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

#52
post #31
post #25

All 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…

I didn't understand why this was an appropriate response. However, I am interested in your browser based ide. Tell me more...

Re: Typing.io: Typing Practice for Programmers

#53
post #38

This is the most stupidest thing I could've ever imagined.

i don't wanna go that far and say that but... I saw this AND belt.io. and im just not seeing any reason for either... like i've tried thinking for a while and have thought of NO USEFULNESS for either tools.

Re: Typing.io: Typing Practice for Programmers

#54
post #31

Earlier quoted context omitted.

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…

I didn't understand why this was an appropriate response. However, I am interested in your browser based ide. Tell me more...

check my profile, there is a link.

Re: Typing.io: Typing Practice for Programmers

#55
Implementation's good, but the concept and idea is completely useless at least for Objective-C/Cocoa. All the symbol names of the Cocoa are strictly designed to be used with auto-completing IDE support, not bare editor. That's why they're fine to go such long names. The IDE is a required part for development just like Smalltalk.

And a lot of other language/libraries/frameworks are also silently presume auto-completion support. Even on C/C++. I highly doubt usefulness of this even on other languages.

Maybe it would be more important to be familiar with specific auto-completion IDE behavior rather than training yourself to type faster.

Re: Typing.io: Typing Practice for Programmers

#56

This 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.
Post reply on HN