Hacker News Reader

Not that fast, but that is mainly because I am a noob, and I take pride in trying to avoid writing shitty code. Insted of just hammering away at the keyboard and using whatever just works I spend some time to make my code more redable and easy to maintain. Also, since we use TDD we end up writing a lot of tests for each pice of code that goes in to our product.

View on HN

If you're really a noob, I'd try to be a little less careful, personally. The best way to stop writing shitty code is to write a whole lot of it so that you realize why it's shitty, not to blindly follow best practices from the start.

Of course, if you're writing production code at work or something like that, it's another matter, and you should obviously try to make sure everything that gets checked in is good quality. But for me, at least, knowing what not to do in the abstract never made the same impact as doing horrible things in my code and then feeling the pain later on - the personally earned lessons are the ones that I remember the best.

Reply on news.ycombinator.com