Hacker News new | past | comments | ask | show | jobs | submit login

I used to buy a lot of technical books, but the last few books on topics like programming or web development that I bought are still sitting on my shelf mostly unread, and I'm not sure I've bought any new ones for several years now.

There is a simple reason for that, which has nothing to do with the economics of writing books or even the editorial quality: with the pace of the industry today, the material in a technical book about any specific development tool or technique or language may well be obsolete before it even hits the shelves.

If there were more technical books with general accumulated wisdom, insightful analysis, and advice that will stand the test of time, I'd be interested. If they had good production quality and editorial standards, I'd be even more interested (because frankly, hardly any of the last few computing books I bought did, even those from supposedly respectable publishers).

But take a look at the new releases lists on Amazon, and certainly at the bestsellers lists or what you find in a bricks 'n' mortar bookshop, and almost everything published in the past few years has either a version number or a "for dummies/beginners" tag in the title. Chances are that I can get material at least as good, often much better, and almost always more up-to-date, just by identifying a few experts on-line and browsing their blog/articles/project docs. Printed books are obsolete as a mechanism for conveying information on these subjects.

In short, there are a few classics in computing fields that still sell well, but how many books destined to become classics have been published in these fields in the past decade? And for anything that isn't, why would anyone buy the limited, ephemeral book when the Internet exists?




In general, I agree with you. But one counter-example would be my experience with Hive in Spring 2013. Our team of four had to ramp up on a very aggressive deadline without knowing anything about Hive. One of my colleagues picked up the O'Reilly book on Hive, and it was by far the most extensive, comprehensive, and convenient reference. The online resources I found were either outdated, incomplete, or would take much more time to find the answer I was looking for.

Another example would be several months later, when I got a job at a company with a lot of Hadoop work, not having much experience with writing MapReduce code. I had two weeks between jobs, so I picked up 4 books on Hadoop. It's less than a day's salary, and allowed me to feel like I could hit the ground running at the new job (and I did). Those books are all outdated now, but I still feel like I got my money's worth from them.




Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: