Computer architecture a quantitative approach by Patterson and hennessy It’s the real life exchange rate for algorithms and data structures. Basically understanding your infrastructure and its performance characteristics will help you design simpler ( and therefore better )systems
FROM THE HN SHELF
Computer Architecture: A Quantitative Approach
John L. Hennessy and David A. Patterson
Computing · A BOOKTypographic jacket · original cover not fetched
FROM THE SHARED SHELF · 2006–2026 SAMPLE
Computer Architecture: A Quantitative Approach
John L. Hennessy, David A. Patterson
6 readers recommend it across 4 discussions
Topics are model-inferred labels.
Keep it on your reading list
THE WORD OF MOUTH
What made it worth passing on?
Original Hacker News comments, in the readers’ own words.
'Computer Architeture: A Quantitative Apporach" and/or more specific design types (mips, arm, etc) can be found under the Morgan Kaufmann Series in Computer Architeture and Design. "Getting Started with LLVM Core Libraries: Get to Grips With Llvm Essentials and Use the Core Libraries to Build Advanced Tools " "The Architecture of Open Source Applications (Volume 1) : LLVM" https://aosabook.org/en/v1/llvm.html "Tourist Guide to LLVM source code" : https://blog.regehr.org/archives/1453 llvm home page : https://llvm.org/ llvm tutorial : https://llvm.org/docs/tutorial/ llvm reference : https://llvm.org/docs/LangRef.html learn by examples : C source code to 'llvm' bitcode : https://stackoverflow.com/questions/9148890/how-to-make-clan... (https://stackoverflow.com/questions/9148890/how-to-make-clang-compile-to-llvm-ir#9149406)
Also recommended in this reply
Computer Architecture: A Quantitative Approach by John L. Hennessy the creator of MIPS and David Patterson the creator of Berkeley RISC (later SPARC) Advanced Programming in the Unix Environment by W. Richard Stevens
Also recommended in this reply
Interesting that this book is mentioned in this thread several times. I didn't find this book bringing almost any value to me. What it did was giving names (e.g. orthogonality) that I didn't know before to the common programming concepts that all developers with some practical experience should be aware of anyway as a common sense. But that might just be due to a different approach to programming. I find the books such as Andrew Tanenbaum's "Computer Networks" which are bringing historical perspective as well as a lot of technical information without going into the tiny details the best balance of useful and interesting. Therefore "Computer Architecture - A Quantitative Approach" is much better for me in that aspect and the C programming should be really interesting too, although I haven't read it.
Also recommended in this reply
- The Pragmatic Programmer (Hunt/Thomas) - Computer Architecture - A Quantitative Approach (Hennessy/Patterson) - Expert C Programming - Deep C Secrets (van der Linden) I woud call the Pragmatic Programmer though by far the most influential.
Also recommended in this reply
First part of the question (actual influences): 1) Philip and Alex's Guide to Web Publishing (not strictly a book). http://philip.greenspun.com/panda/ 2) The "Dragon Book" https://en.wikipedia.org/wiki/Principles_of_Compiler_Design 3) Computer Architecture: A Quantitative Approach Second part (at hindsight): 1) https://en.wikipedia.org/wiki/Rich_Dad_Poor_Dad (cheesy, but useful) 2) http://toddkashdan.com/upside.php 3) https://www.schranner.com/de/news/2012/04/16/-verhandeln-im-... (https://www.schranner.com/de/news/2012/04/16/-verhandeln-im-grenzbereich-und-teure-fehler-jetzt-auch-im-apple-ibook-store) - German book about negotiations written by an experienced hostage negotiator.
Also recommended in this reply