Hacker News Reader

Coding speed is absolutely not the problem that needs solving. What is needed is how to do more with less code. Long term maintenance of massive code-bases is the hard bit that eats away at productivity.

Writing unit tests faster absolutely encourages me to write more thorough tests. It’s less about speed to me and more about painlessness. It’s good at the most boring snippets, which I’m happiest to offload.

Treat it as a mildly better autocomplete, and you’ll be happy with it.

Well we have many ways to do it by abstraction — libraries, recipes, patterns, and so on.

I think that this sort of thing will handicap a dev in the same way that learning to write with a spell checker can (does!) handicap writers.

This is how I use it. I ignore anything specific to the logic of what I am writing, but it's great for filling out shit like structs and gets those right. I start typing `type ResponseHandler....` and it immediately knows what I want