3 ms·
From the pov of my career: Designing Data-Intensive Applications is the only technical book I've ever read that I felt was worth the time it took me to read it.
by whoooooo123 4y ago
From the pov of my career: Designing Data-Intensive Applications is the only technical book I've ever read that I felt was worth the time it took me to read it. It's excellent - I learned a ton, I keep going back to it, and if I'd read it as a fresh graduate it could have saved me a lot of trouble.
I've read a few other of the popular programmer books eg Clean Code, Refactoring, the Pragmatic Programmer, Working Effectively With Legacy Code, and I didn't get much value from any of them. They're not bad, it's just that they didn't teach me much that I hadn't already picked up on the job, and I didn't feel like a book was the best way to learn their lessons as opposed to just picking up what you need to know from Google, colleagues, etc, over the years as you gain experience.
- hardlianotion 4y agoWhat was your approach to reading and getting value from it?
- whoooooo123 4y agoSlowly and methodically, taking lots of notes.
- jmcgough 4y agoReading DDIA right now and I second this - the best technical book I've read, still holds up well after five years.