The Pragmatic Programmer says that you should try to read a technical book once a month. I believe you should read at least 4 technical books a year but also agree that you should aim for 12 books a year.<p>So, how many technical book do you read a year?
I'm probably an outlier. I read around 15 technical books per year. I read them because I enjoy their content: beautiful books like SICP, TAOCP, Stevens' books, etc.; I can recommend them to anyone. There are plenty of tech books out there that are awfully boring though (I don't read those). Funny enough, people usually say that books like the former (the beautiful ones, the timeless ones) don't help you on your current job... Well, I couldn't care less. I don't read sci-fi to gather knowledge either. I read for fun, and this applies to tech books as well.<p>(I believe that timeless tech books do help you, though. They help you with your career, not with your (current) job).
I don't get hung up on numbers or whether I actually "finish" the book.<p>It is a lot easier to read a book like The Pragmatic Programmer cover-to-cover than it is to read a book about a specific language or API. I've been trying to learn Rust and I find that if I don't practice or do exercises then I don't end up remembering what I read. I read nearly all of "Programming Rust" but now I'm having to go back and read many sections because I wasn't writing the code as I was reading the chapters.<p>As for "finishing" books, I rarely truly finish a book. I've been reading graphics and game engine books but I don't feel pressure to read every chapter. Did I really "finish" a book if I skipped chapters? Who cares. Every graphics/game book seems to start with chapters about linear algebra so I skip those. Collision detection? If I need to find the intersection between a line and a cone then I'll look it up.<p>I also find it helpful to read a chapter from multiple books about the same topic (thanks to o'reilly books online). Like when I was learning C++11 I read the futures/promises chapter from 4 or 5 different books. I found having the same thing explained by different authors was more helpful than just re-reading a chapter. I also had a learning disability as a kid so maybe that's why I need to re-read things so much.
Zero.<p>I totally appreciate the value in it, but I'm old and just have a hard time making personal growth in my job skills a priority over time with family. I read more before I had children, and I would read if I was could spend some work hours on it.<p>I've also seen people who read too much - all their work philosophy and decisions are not based on experience, but on a book they read. I feel the flow should be to: read -> synthesize new info with experience -> test out some changes to your way of working -> decide whether or not it works. But I've seen too much of: read -> declare sweeping changes to the entire team -> read another book.
I read a lot. I basically always have at least one fiction book and one technical book (usually math, statistics, or programming) that I'm reading at any given time.<p>I think I'm an outlier on the other end. This year I've read 3 or 4 books on programming language theory, one specifically about Scheme, and The Rust Book. I've picked up and read a a little bit to a lot from a lot of math textbooks.<p>This is all probably stems from graduate school training and my ADHD... It also helps to have PDFs or online versions and a baby that had some serious aversion to sleep, so the only thing you can do is sit in the dark rocking her and read...
Reading is my only hobby right now (I'm able to fit it in around kids) so I aim for 3-4 books a month. Most of what I read is non-fiction, but technical books take a long time to finish so I'd say I finish ~10 technical books a year.<p>I won't say I remember everything I read, but I highly recommend reading as much as possible. My career has been on an upswing the past few years and I have to think reading more has been a contributing factor.<p>Reading has been particularly helpful at my current job where I don't have any mentors or more senior people to learn from, books have helped fill at least some of that gap.<p>Context: I am a software engineer / architect with 8 years full time dev experience.
I have been "reading" Crafting Interpreters for about a year, and implementing variations on what it is teaching. I always try to have one on the go for 10% time or whenever I'm out of original ideas. Got SICP but expect that to take another 3 years at this rate.
one, maybe two? One technical book a month sounds like way too much provided you actually aim to <i>work</i> through the book thoroughly. I recently made my way through SICP because I never finished it when I was studying and that took me like half a year during my free time.
I think it's more important to ask: how much have you _learned_ from reading technical books?<p>There's also different reasons for reading technical books: getting answers to current problems (though most people would just search the web); going deeper on a specific topic that you're already familiar with; tackling a new area; etc.<p>While I read a lot of pieces of books, I find reading in a group (book club[0]) to be the best way to really understand what's read (as well as providing a bit of discipline and structure to make sure I really read it and don't just skim/skip).<p>[0] This is why I run a weekly book club as part of my Discord community (<a href="https://ted.dev/discord" rel="nofollow">https://ted.dev/discord</a>), so I know I'll deeply read at least a few books every year.
It depends on what I need. If the company gets into some new technology then I read a couple of books on the topic. I try to get generalist books instead of framework x.yy books.<p>So, it can be 4-8 books or none depending on the year.
As a data point, I've purchased (or borrowed from the library) 9 technical books this year. I've read bits and pieces of all of them, but I haven't read them cover-to-cover.<p>By then end of the year, I'll probably be up to 12-15 total, but not reading everything.<p>Edit: I probably read about 1/4 to 1/3 of each book (although this varies widely), so that puts me at ~4 full books.
I've read about 1-2 per month so far this year, but I'm burnt out now and I plan on hopefully not reading any more technical books this year. Also I find I don't really remember much from them, but I don't take notes etc, I am more of the 'something will rub off on you' persuasion when I read books.