4 ms·
No TAOCP or even The Mythical Man-Month?
by teddyh 7y ago
No TAOCP or even The Mythical Man-Month?
- microtherion 7y agoTAOCP is a wonderful coffee table book, but I don't think I've ever seen somebody use it on a day to day basis.
- mangamadaiyan 7y agoIt isn't really the kind of book you use on a day-to-day basis; you consume it in small doses (after crossing the initial cliff of notation, et cetera), like vitamin supplements. That doesn't make it any less useful, however.
- dfox 7y agoToday having physical copy of TAOCP is mostly only useful as the coffee table/conference room artifact. All the stuff in there is either well known because it is part of basic CS curriculum, better analyzed by subsequent works or mostly irrelevant.
- klodolph 7y agoMy personal experience is that anything in TAOCP can be found elsewhere in a more accessible format.
- svat 7y agoThat's interesting; my personal experience is the opposite: for most things in TAOCP, it is written more clearly than its source material, especially as it gets to the more advanced topics within each section (often only published in papers, not yet in books). For example, Section 7.1.4 on Binary Decision Diagrams, aka BDDs and ZDDs (pages 202–280 of Volume 4A, draft online: http://www.cs.utsa.edu/~wagner/knuth/fasc1b.pdf http://www.cs.utsa.edu/~wagner/knuth/fasc1b.pdf) is not something I've seen explained to that level of clarity and detail anywhere else. Plus there are a lot of Knuth's original ideas in the books; his innovation is not restricted to summarizing and teaching.
- frans 7y agoTAOCP = The Art of Computer Programming by Donald E. Knuth
- svat 7y agoSorry, I don't understand: could you clarify why you're telling me this? Was there anything in my comment that seemed like it was talking about something else?
- lioeters 7y agoI think the parent comment was trying to be helpful for other readers who might not know what TAOCP stood for, since it wasn't defined from the beginning of the comment branch. For what it's worth, I appreciated your defense of the book, that there's genuine value in reading it, rather than as a "coffee table book" (I guess social signalling); that Knuth explains things clearly and in detail, with unique approach and insights.
- svat 7y agoAh that makes sense, thank you. Always good to explain acronyms; it just didn't occur to me that it was a reply to the whole subtree of comments, so I was confused how to respond.
- deleted 7y ago[deleted]
- wglb 7y agoBack in the day, we had to write floating point routines before there was 80387. We had the appropriate chapter of TAOCP open during the whole project. Also, if you read Programmers at work, it was the knowledge of the one rarely taken step in the long division algorithm that enabled one of the subjects to debug a process that had no tools.
- dickeytk 7y agoI'd pick SICP over those 2
- atomicity 7y agoJust wondering, why is TAOCP or SICP (as mentioned in a child) essential? I've always considered reading them since I hear about them all of the time but I could never really relate it to the work that I do (around distributed systems and storage). I'm sure the material in the books is useful, but are these books must-reads? In databases, there is Readings in Database Systems (http://www.redbook.io/ http://www.redbook.io/). I wouldn't recommend it as an essential to all engineers and researchers, because one would be better off spending their time learning practical skills that apply to their job (relevant tools, protocols, etc.), gaining a broader understanding of CS, and exploring general topics (work/career, teamwork, enjoying life, etc.). In the same vein, it feels like SCIP and TAOCP go too far in-depth into topics that aren't that important to everyone. I rarely see the topics in these books pop up in the research papers that I read (though I mainly read systems ones). I definitely don't see them when I'm building REST services or Javascript frontends. When I check on the Table of Contents in these books, I never feel like reading a chapter in the book would have saved me a ton of time in the past. As a result, I've concluded that they a good intro/intermediate CS reference for people who'd be interested in the research/theory side of things. Still, I've seen them recommended so much that it bothers me. Have you all seen anything in these books that truly makes them required readings?
- playing_colours 7y agoThere are other “sacred” books: - SICP, - Concepts, Techniques, and Models of Computer Programming, - Paradigms of AI Programming: Case Studies in Common Lisp, - Elements of Programming. I got them all at some point in my career in order to become a top notch engineer. I have not finished any of them yet, 10 years later. I think they are great and you can learn from them a lot, particularly I found CTMCP to be very informative. Problem is they require dedication, and I think one gets the most from them by consuming them sip by sip meanwhile coding a lot and integrating new techniques and mental models. EDT: formatting