Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

I try to avoid programming books. When reading I prefer being disconnected, laying down in a comfy sofa/bed with a hot beverage. Programming books doesn't work very well for me because they make me want to try out the things I read about, forcing me to be at the computer. Some of them even assume you are sitting at the computer, ready to run examples..

If the goal is to improve as a programmer and books being the medium I choose books that doesn't necessarily have an obvious link to programming but benefit my thinking around it. Books on design, architecture, media and education being my favourite. I don't follow any particular techniques but have grown into some habits (reading ~50 books a year). I read multiple books at the same time (~3-4), usually very different in style/topic, alternating between them. This way I never get bored. The new books I choose for reading has to spark some excitement/passion in me, otherwise I'm never going to finish it. It could be as simple as some concept in a book that triggers curiosity, then I just follow the reference/bibliography and further do some quick research (amazon/goodreads) to see whether it looks like a promising book.

Reading about product design will make you a better software designer.. Reading about media will make you see how your application fits in a bigger picture.. ..and so on.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: