3 ms·
I've been working through the first volume in a reading group with a few friends. Some chapters are definitely better than others, and it often requires awaren
by dllthomas 6y ago
I've been working through the first volume in a reading group with a few friends. Some chapters are definitely better than others, and it often requires awareness that it captures a snapshot of thinking from ~10 years ago, but it's been a good experience.
- p1nkpineapple 6y agoCould you please elaborate on the chapters that you feel are the best to study? Cheers!
- dllthomas 6y agoSo far we've read the chapters on Asterisk, Audacity, Bash, BerkeleyDB, CMake, Continuous Integration, Eclipse, and Graphite. Of these, I liked the chapters on Bash, BerkeleyDB, and Graphite better than those on Asterisk, Audacity, CMake, and CI. I had trouble getting through the chapter on Eclipse, although there were some interesting bits. The chapter on Bash suffered a little, in my personal experience, because about 70% of it was a rehash (with a slightly, but not sufficiently, different perspective) of information present in the Bash man page, which I had previously read in a reading group with some of these same people. But really, the chapter that's best to study is probably the one you're currently most interested in, even if it's "not as good" as another considered in the abstract. Just remember not to assume that the entire book is of the same quality, whatever your experience.