Slashdot Mirror
Best Computer Books For The Smart
You'll remember last week, I asked for recommendations of the Best Websites for developers. This was a -great- thread and in the story, I mentioned that I was planning on doing the same regarding books this week. So here it is. What do you, the slashdot reader consider seminal works? What would you consider great introductions to technical topics? If you are interested, check it out...
As part of this I'm looking for books on C, C++, Perl, Python, PHP , System Administration, anything...you name. As before I have opinions on great books, but I want to see what you think. Also, what do people think is a great introductory book for people new to linux.
Effective C++ and More Effective C++, by Scott Meyers
by Bruce Schneier. The book is enjoyable and has saved me from several gaffes when using crypto for applications.
demi
Programming Perl (Camel)
Perl Cookbook (Bighorn sheep)
Anything with Knuth's name on it
Dragon Book (Compilers - Principles, Tools & Techniques, Aho et al)
Gang of Four (Design Patterns, Gamma et al)
Andy Tannenbaum's OS book
That thick ass Intro to Algorithms book from the MIT boys
Patterson/Henessey Computer Organization & Design
The One Rule Of Chess You'll Ever Need: Don't play someone who carries a kit in their bookbag.
Design Patterns, by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides.
Refactoring: improving the design of existing code, by Martin Fowler, Kent Beck, John Brant, William Opdyke, and Don Roberts.
Joe Celko's SQL books.
It's an introductory text, but Jerry Sussman's and Julie Sussman's Structure and Interpretation of Computer Programs is pretty good too. It makes you think about things more deeply than many other books do.
Introduction to Algorithms - Cormen, Leiserson and Rivest
- Great book, little bit of everything.
Code Complete - Steve McConnell
- Must read for anyone serious about programming. Read it.
Advanced Programming in the UNIX Environment - Richard Stevens
- Still one of the best UNIX programming books I've seen.
Since the advent of the web, though, I've come of the opinion that language agnostic books are the important ones. Books on particular languages ("Learn Foo in 21 days", "Practical Programming in BarBaz") or technologies date way too quickly. The web is the best source for information like this.
I think we're thankfully seeing more books like "Pragmatic Programmer", the "Extreme Programming" series, "Design Patterns", "Refactoring", "Death March" and other books that transcend particular languages and technologies.
- Theoretical background -- experience in a CS course, good books that give you a theoretical base are nice. Why? Because later, to translate the theory into real work, you'll just need a reference, and things will work easier!
- Reference books -- to learn how to implement your ideas in specific settings (OS, language, etc).
I never found the first with books for specific compilers, IDEs, versions of things, etc, or any of those "big" books that promise you a lot.Interesting choices are books written "by the language author" (think Stroustrup, Larry Wall, etc), or books by people with a good background in CS (a CS professor, for example).
Also, books on theory are interesting. A book on Compilers may change the way you think. (The old "Dragon" book is nice, and Andrew Appel's book is also interesting). One book on Analysis of Algorithm like the one by Cormen, Leiserson, Rivest and (forgot the third author) is quite good, but you need a decent math background.
And for a reference, I think the more compact the better (I use Java in a Nutshell). References shouldn't be more verbose than the necessary.
(Just my $0.02)
You might also mention his book "On LISP", which
is now out of print, but can be downloaded from
his webpage.
On LISP goes into LISP issues much deeper than
ANSI Common LISP.
For Java, a smart person with a little computer background should be able to figure it out from the language definition. Any of the more complex topics in Java change so quickly that it isn't worth buying books on them anyway--just use the on-line references. Sun has on-line tutorials ("trails") at developer.java.sun.com, left over from the days when Java wasn't hot yet and when they still had to bother recruiting people to Java.
For Perl, I wouldn't bother with any kind of reference. Just find scripts that roughly do what you want and hack them; it's blind groping around, but that's the way Perl works. If you can't get it to work that way, you probably should be writing in something else other than Perl. If you must, get something like the Perl Cookbook and a quick reference guide.
For Python, I like "Python and Tkinter Programming" and "The Quick Python Book", although O'Reilly's reference is also decent.
For a fun yet challenging introduction to computer programming, "Structure and Interpretation of Computer Programs" is good. What makes it even better is the fact that it's a book that teaches modern abstraction techniques but does not rely on object-oriented programming for everything. Most people coming to computers and computer programming wrongly think that objects are either the best, or even the only, way to build abstractions.
Check out http://www.canonicaltomes.org/, people have entered and voted on the "best" books in a variety of categories.
Sorry if I'm too lazy to look up any links or authors.
Thinking in C++/Java
Algorithms in C, the whole series.
Design Patterns by Erich Gamma, Richard Helm,Ralph Johnson, and John Vlissides.
Hidden Order: How Adaptation Builds Complexity and Induction : Processes of Inference, Learning, and Discovery both by John Holland - father(?) of the genetic algorithm - not necessarily computer books, but they do provide a different perspective on how you can write software to do thing.
The Art of Computer Programming, Volumes 1-3 by Donald E. Knuth
"For a successful technology, honesty must take precedence over public relations for nature cannot be fooled." -Feynman
I have no doubt that if you want to have a more theoretical background on many subjects regarding Computer Science, you have to read (or, at least, take a glance at) Knuth's The Art of Computer Programming.
His books give an excellent introduction to many subjects, including many of the hardest problems in Computer Science. The first volume of his "The Art of Computer Programming" gives a very concise and comprehensive review of Mathematics needed for the remaining volumes. You might even learn about mathematical objects you never heard of (if you don't have higher education in Mathematics).
If you need something ligther on the Mathematics needed for Computer Science, then you might want to read his "Concrete Mathematics". Quite a beatiful book (typographically speaking), with an outstanding expostion of some advanced topics in Mathmematics neede for Computer Science and also quite funny to read.
I should also mention that his books are also a prime example of how someone should write a book. His books, while mostly technical, show a clear style of writing, direct and also entertaining, while discussing deep subjects.
The "problem" with Knuth's books are that they are intended for serious readers. You know if you are serious if you can read the first pages of his first volume. :-)
Another book that I would recommend is Andrew Tanenbaum's "Modern Operating Systems" (which is a bit more practical than Knuth's books) gives an overview of the structure of some common Operating Systems, including DOS and Unix.
I could give you many other recommendations, but you'd have to specify if the other recommendations that you want are more practical or more theoretical.
I hope this helps.
1. K&R, The C Programming Language, 2nd ed.
2. R. Stevens, Unix Network Programming, 2nd ed.
After that one should decide what to choose. If it's C++:
B. Stroustrup, The C++ Programming language
After that people usually can find their way around books on their own.
Contrary to the popular belief, there indeed is no God.
under the circumstances, than "SQL For Smarties"? ;-)
No joke, it really is a good book!
"There is more worth loving than we have strength to love." - Brian Jay Stanley
For everything (well, almost) C++, you need the C++ in depth series. Get it, it's a great package.
Contains More Exceptional C++, Exceptional C++, Essential C++, Accelerated C++ and Modern C++ Design.
Accelerated C++ is the best book teaching C++ from the ground up that I have ever seen. It's worth getting and reading even if you think you already know the basics. Really.
Belief is the currency of delusion.
Code Complete and Rapid Development are the kinds of books I find most useful. I don't like any books that are specific to a language. These two are fantastic resources for learning how to program better, not how to write in a particular language.
Specifically Unix Network Programming (vols 1 + 2) and Advanced Programming in the Unix Environment. Basically the holy bibles of all things unix-programish.
;)
Aside from that, same as what others have mentioned... Applied Cryptography, Unix System Administration, Practical Unix & Internet security...
Oh yeah, "The Complete Canadian Small Business Guide" has come in handy in many instances indirectly related to programming...
"People will pay big bucks for the luxury of ignorance."
SICP.
(Structure and Interpretation of Computer Programs, a fine book that'll teach you more about programming than should be allowed by law)
A decent list of C++ books is in this newsgroup posting.
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
Zoroaster: The Avesta
Lucretius: On the Nature of Reality
Marcus Aurelius: Meditations
Immanuel Kant: Critique of Pure Reason
Albert Einstein: Relativity
Then, more specific for developers:
..and
..by me. ;-)
The Lord of the Rings. (doh)
Hitchhiker's guide to the Galaxy.
How to date a woman.
Definitive guide to mental and sexual masturbation.
<^>_<(ô ô)>_<^>
Aho, et. al. "Compilers"
Alexandrescu, "Modern C++ Design"
Bentley, "Programming Pearls", 2nd ed.
Brown, et. al. "Antipatterns"
Cooper, "About Face: The Essentials of User Interface Design"
Fowler, "Refactoring"
Gamma, et. al. "Design Patterns"
Hanson, "C Interfaces and Implementations"
Johns & Lins, "Garbage Collection"
Josuttis, "The C++ Standard Library"
Kernighan & Pike, "The Practice of Programming"
Kernighan & Ritchie, "The C Programming Language" 2nd ed.
Knuth, "The Art of Computer Programming" vol 1-3
Meyers, "Effective C++"
Meyers, "More Effective C++"
Meyers, "Effective STL"
McConnell, "Code Complete"
McConnell, "Rapid Development"
Plauger, "The Standard C Library"
Stroustrup, "The C++ Programming Language"
Stroustrup, "The Design and Evolution of C++"
For specific topics:
Foley, et. al. "Computer Graphics"
Kernighan & Pike, "The Unix Programming Environment"
Schneier, "Applied Cryptography"
Stevens, "Unix Network Programming"
Stevens, "Advanced Programming in the Unix Environment"
Also the Graphics Gems and Game Programming Gems series are superb. Maybe my list makes me old-school, but I like to understand what is happening from the use case all the way down to the register allocation algorithm. Of course, I can't always do that.
I don't mention any Java books because they get outdated so fast. The language hasn't changed much since 96, but the class library api is in constant flux.
union select * from books where author = 'R. Stevens';
bla
Not sure if these are for "the smart" but here are a few books that I've enjoyed. They make for nice easy summer reading -- and ya might learn somethin too!
The Pragmatic Programmer: From Journeyman to Master -- A excellent guide to help you go from spagetti coder to a professional programmer.
Programming Pearls (2nd Edition) -- Elegant solutions to interesting problems.
The Practice of Programming -- Coding style, algorithms, etc.
Titles that are more meaty would include Code Complete, Design Patterns, Refactoring, Applied Cryptography, Knuth, etc., but I'm sure these will be mentioned ad nauseam.
The three Edward R. Tufte books...
"The Visual Display of Quantitative Information" Graphics Press; ISBN: 0961392142; 2nd edition (May 2001)
"Envisioning Information" Graphics Press; ISBN: 0961392118; (May 1990)
"Visual Explanations: Images and Quantities, Evidence and Narrative"; Graphics Press; ISBN: 0961392126; (March 1997)
"How to Do Nothing," kids activities, back in print!
This is the introductory computer programming textbook used at MIT, and had been featured on slashdot here. However it is very different from what you would expect from such kind of books, with Scheme as the implementation language, it really does not teach readers how to code in a specific programming language, but how to program computers in a large variety of paradigms, what are the trade-offs in program design, how to manage complexity, and how the basics of computing works, by stretching the flexibility of the Lisp family of languages to the maximum. I first read it four years ago as a freshman, and it was a real eye opener. And it never ceased to amaze me through all these years, as I continue to discover new insights in the passages.
You can almost find a full undergrad CS program concentrated in this book, with topics including language design and computing paradigms (object-oriented, functional, imperative, non-deterministic and logic programming, as well as lazy evaluation), operating systems (issues of concurrency), architecture (the design of a register machine), and compiler construction (the reader is asked to build a Scheme compiler in the end). Instead of being filled with buzzwords, here you are shown how the basics of everything works, in ways that you can really understand. Working through this book will teach you concepts that many people with a CS degree had never heard of.
Hell, if I could only save one CS book when the world comes to an end, this would be the one. And the best part is: you can get the full-text online here at MIT Press. Definitely a must read.
Two books stand out: "Python: Essential Reference" (2nd edition) for the ins-and-outs of all of Python's built-ins and most of the major modules, and "Python Visual Quick Start Guide," which is sort of like a Python cookbook of the basics, if you're new to it all. These two books have taken care of all my needs.
:Peter
The C++ Programming Language by Stroustrup(Addison)
A quick introduction to Fundamental Design:
Composite/Structured Design by Myers (ReinHold)
For on-time software projects:
Debugging the Development Process by MacGuire (MS Press)
For TCP/IP protocols and issues
TCP/IP Illustrated by Stevens (Addison)
For numerical programming:
Numerical Recipes in C/Fortan/etc by Press, et al (Cambridge)
For what a computer might be like:
The Humane Interface by Raskin (Addison)
For advance C:
C Traps and Pitfalls by Koenig (Addison)
For object-oriented design
Design Patterns by Gamma, et al (Addison)
For general reference:
The CRC handbook by the editors at the Chemical Rubber Company
Now, I have a question. Who is the most reliable publisher of computer books. It seems that O'Reilly is all the craze, but I have been disappointed with their accuracy and editing of late, though I buy their books if they are on discount or the only good text. For example, I bought their PHP book and I saw several mistakes in the programming examples, mistakes which would totally confuse an inexperienced coder. IMHO, the most consistently good books are published by Addison-Wesley. I would like to hear what other people think.
"She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
AC is a fine book if you're reading around to be able to implement protocols and cryptographic algorithms, but if I had to pick one book on cryptology it would be David Kahn's The Code-Breakers. A fantastic book on the history of cryptology. I can't even begin to phantom the amount of research that went into this tome, it's just unbelievable.
Don't get the abridged version, and don't expect this one to be up to date on things happening after WW2 -- but understand that this is not a failing, it's a strength.
It 1100+ pages of pure goodness, and I couldn't put it down.
Belief is the currency of delusion.
... great, classic, book on how to think about problem-solving.
'Godel, Escher, Bach', Douglas Hofstader - for melting down, spinning around and reshaping your mind.
'Structure and Interpretation of Computer Programs' - Abelson and Sussman - read the negative reviews at Amazon to realize how sophisticated a book this is. I found it my senior year in Computer Science and realized I'd hardly learned a thing yet. Deep stuff.
'The Pragmatic Programmer', Thomas and Hunt - wish I'd had it at the start of my career, it'd be even more fun, profitable and far less painful.
'Code Complete', McConnell - The bible of 'how to code it'.
'Software Project Survival Guide', McConnell - got me through my first independent project, with plenty of room for growth. Great book for a newly appointed project manager. Helps developers (and everyone else) figure out if their project is going gold or down the tubes pretty accurately.
'The Mythical Man Month' - Fredrick Brooks. Should be read regularly by anyone who manages software professionals. It's an interview question I ask any hiring manager. Ones who care about the field say 'Yes'.
'Programming Pearls' (any edition), Jon Bentley - Great fun, great exercises, great quotes. When you start feeling like programming is drudgery, a great tonic to renew your appreciation. Full of little techniques and large wisdom.
'Programmers At Work' - Interviews with 1985's leading lights of the software development industry. Great inspiration, now with historical relevance.
'The C Programming Language' - my vote for the most influential computer book ever(Hello?), and full of worthwhile knowledge. Anything Kernighan's involved in is worth picking up, an author who really cares about writing well.
You absolutely need the book on Design Patterns by Gamma et al.
Also you should check out the Antipatterns book by Brown et al. A book on "common pitfalls" and more importantly, possible resolutions.
But, if you want to deviate a bit from the technical books, and if you want to expand your understanding of design and design patterns in software, and the philosophy behind it, you might be interested in Christopher Alexander's books and writings. His books are quite old, published in the 70s.
He's an architect (of actual buildings), but his ideas apply to anything that is designed. He developed the concept of "design patterns" and the computer science world has been applying his ideas. Here is a little article about him. It's because of him that we have the following definition of pattern: a solution (set of forms or rules), which solves a problem (resolves a set of forces), in a given context (a recurring sitution). A very general idea.
Basically he was trying to come up what he calls a "Pattern Language", a high-level way to describe design patterns in urban architecture, so that people could basically design their own homes and buildings. But the end result was something more profound and philosophical. Very interesting stuff but rather touchy-feely at times. For instance when he talks about the QWAN (quality without a name, the mystical sort of "beauty" that a good design has).
He also has (or he's still working on, I'm not sure) a recent multi-volume work called "The Nature of Order". I want to read it and I bet it's a much more interesting and insightful book than Wolfram's recent giant tome about a "new kind of science", and without the hype.
Disclaimer: I'm just getting into this type of stuff so I'm not 100% aware of all the history, etc., but Alexander's the name I see everywhere.
The Standard C Library,P.J. Plauger
I use this book *all* the time. It's very informative to see how a C library implementation works, and it has the important sections of the C standard reprinted with discussion. My #1 pick.
Advanced Programming in the UNIX Environment,W. Richard Stevens
The comp.unix.programmer bible. A must have for UNIX programmers.
UNIX Network Programming Networking APIs: Sockets and XTI, W. Richard Stevens
Another classic from Stevens. I have not done a tremendous amount of socket programming in C but I have extensively in Java and I am confident that I can in UNIX after having read select portions of this obviously high quaility book.
Lex & Yacc, John R. Levine
I think yacc (the GNU version is called bison) is an extreemly usefull tool. I started writing yacc grammers for all sorts of configuration files on my system while reading this the first time. Great fun, and potentially very usefull. A good yacc grammer can save tremendous amounts of time and is often the proper way to handle a problem. And I'm not recommending the book just because it's the only of it's kind. It's genuinely good.
Algorithms on Strings, Trees, and Sequences Computer Science and Computational Biology, Dan Gusfield
This is a tough book. Be prepared to ponder the presentation of each algorithm and skip the proofs (I believe you Dan). If you find yourself getting stuck in spegetti string manipulation, implement a few of these algorithms like calculating the edit distance of two sequences or Boyer-Moore. You'll be a better programmer after and there are very practical application hidden in this book. Again, the presentation is of the highest quality.
Introduction to Algorithms, Thomas H. Cormen, Charles E. Leiserson, Ronald L. Rivest
I have three algorithms books. This one's the best and that's not a compermise. It's a great book.
The C Programming Language, Brian W. Kernighan, Dennis M. Ritchie
Of course.
The Art of Computer Programming (Vols 1-3), Donald E. Knuth
The C++ Programming Language (Third Edition and Special Edition), Bjarne Stroustrup
Xlib Programming Manual, Adrian Nye
Applied Cryptography: Protocols, Algorithms, and Source Code in C, 2nd Edition, Bruce Schneier
X Window System Toolkit, A Complete Programmer's Guide and Specification, Paul J. Asente, Donna Converse, Ralph R. Swick, Paul Assente
Expert C Programming, Peter van der Linden
Life with UNIX, Don Libes and Sandy Ressler
Programming Pearls, Jon Bentley
Structured Computer Organization, Andrew Tanenbaum
The Code Book, Simon Singh
Etudes for Programmers, Charles Wetherell
Secrets and Lies, Bruce Schneier
The Pragmatic Programmer, Andrew Hunt and David Thomas
TCP/IP Illustrated, Richard Stevens
Exploring Expect, Don Libes
UNIX System Administration Handbook, Evi Nemeth et al
If you use UNIX, you need this book. Forget Running Linux. This is much better and the latest edition covers Red Hat as well as BSD, Solaris, and HP/UX.
Digital Woes, Lauren Wiener
Surely You're Joking, Mr. Feynman!, Richard P. Feynman
This was a pretty funny book. Very readable for anyone. A NYT Bestseller.
Structure and Interpretation of Computer Programs, Harold Abelson, Gerald Jay Sussman, and Julie Sussman
Essentials of Programming Languages, Daniel P. Friedman, Mitchell Wand, and Christopher T. Haynes
Software Fundamentals: Collected papers, David L. Parnas, Daniel M. Hoffman and David M. Weiss
The Invisible Computer, Donald A. Norman
Lion's Commentary on UNIX 6th Edition, with Source Code, John Lions
Envisioning Information, Edward R. Tufte
The Visual Display of Quantitative Information, Edward R. Tufte,
I think I have this book. I was disappointed.
Visual Explanations, Edward E. Tufte
The Design of the UNIX Operating System, Maurice J Bach
Algorithms in C, Robert Sedgewick
Not that great. Having lot's of code samples is nice but the comments are unbelieveable. Their HUGE. Really ruins and otherwise good book. I'd rather go with the Cormen book on Algorithms and just write c from there (done just that many times actually).
Introduction to Computer Theory, Daniel I A Cohen
Compilers, Principles, Techniques and Tools (The Dragon Book), Alfred V Aho, Ravi Sethi, and Jeffrey D Ullman
The Practice of Programming
Kernighan, Brian W., and Rob Pike
The Mythical Man-Month, Anniversary Edition : Essays on Software Engineering, Frederick P. Brooks
"The Mythical Man-Month", Brooks. Won't really help much, but you'll have the satisfaction of knowing exactly how your pointy haired managers are screwing things up.
"Design Patterns", Gamma, et al. Without this, you simply won't be able to understand current discussions about programs or programming. This book gives you the philosophy and vocabulary to understand what's going on.
"The Art of Computer Programming", Knuth. What can I say? An absolutely mindboggling treasure trove.
"Software Tools", Kernighan & Plauger. A Golden Oldie. The book is ancient, but the "software tool" concept is still solid.
"The Design of the Unix Operating System", Bach, and "The Design and Implememtation of the 4.4 BSD Operating System", McKusick et al. (These are old. I would hope there is something equivalent for Linux and current BSDs). While abstraction is all well and good, at some point you have to open up the black box and figure out what the machine is actually doing in there.
You need the definitive description of the language you're working with. For C, it's "The C Programming Language", Kernighan & Richie. For C++ it's "The C++ Programming Language", Stroustrup, or, if you're a standards junkie like me, INCITS/ISO/IEC 14882-1998, "ANSI Standard C++".
If you're doing anything connected with the Internet, learn about RFCs. Personally, I credit a large part of the success of the Internet to the free availability of its governing standards. (Other standards are freely available, but not available for free. A paper copy of ISO 14882, for example, is US$175.)
There are all sorts of "domain specific" books. What you need depends on what you're doing. I find "Advanced CORBA Programming with C++", henning & Vinoski, to be priceless, but then, I do CORBA programming in C++.
Welcome to the Turing Tarpit, where everything is possible but nothing interesting is easy.
As I interpret the question, seminal works on technical topics of all sorts qualify. In that spirit, I most highly recommend "Calculus Made Easy" by Silvanus Thompson. Originally written in 1910 (I think. It's recently been republished), this is the book that finally enlightened me. After 3 years of advanced mathematics and an engineering degree, everything I knew about calculus was rote: I could come up with the answers, but not because I understood the underlying principles or basis, but because I could memorize procedures. After I got this book and read it, I finally understood what the hell it was all about. I don't know whether I was just a bad student before, had bad teachers, or simply was presented the material in a way that was incompatible with the way I learn. In any case, this book did it for me, and perhaps it will do the same for others.
One caveat: I read the original, not the current version, which Amazon says "In this major revision of the classic math text, Martin Gardner has rendered calculus comprehensible to readers of all levels." I'm loathe to recommend a book that I considered perfect in its earlier incarnation and that someone has 'revised,' so perhaps you'll want to search for the original.
If you truly believe that those are the ten most important algorithms of the 20th century, you really need a change in perspective. Quicksort could certainly be put forward as one of the most important algorithms of all time in computer science. Most of the remaining algorithms mentioned are important for their mathematical basis and/or their contribution to the field of engineering, not for their contribution to computer science.
And of course, in order to make any use of these algorithms, it is important to have a good implementation of them. If you don't know how to write those "frickin for loops" and how to make use of your development tools of choice, you're going to get nowhere real fast. It's true that from a computer science perspective, many development languages or features in them are isomorphic and once you've learned it once, the rest is mostly just a different syntax. But you do have to learn it once, and well.
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
I think that was always true beyond a certain point. Most developers follow the same path: they start out with specifics (their first language, a particular I/O library) and as they learn more specifics, they start to see the generalities (procedural/OO/functional/etc. approaches, "pseudocode" for algorithms, concepts like controls/widgets and event-driven code in GUIs). There is always a need for good information on any given tool, be it a programming language, a library or whatever, but the distilled knowledge that transcends any specific tool will always be more useful for longer.
That I have to disagree with, though. The web is a great source of information for a few languages, particularly the less popular ones. It's a lousy source of information on good programming technique in many (C, C++, Java, etc), because most of what's there is written by enthusiastic but ill-informed authors, and they simply spread their poor style or incorrect knowledge.
Most languages do not change so fast that a good book will date too quickly to be useful. In various places I've programmed, there have been plenty of books on the shelf covering C, C++, Java, Python, Perl, FORTRAN and other languages, many dating from several years ago but still just as relevant today. Sure, there come certain cut-off points; books with only the Java 1.0 library in them or dating from before the C++ standard have limited use, now. But those cut-off points are relatively rare. Reading a good book takes only a few days, and even if the benefits last for a year or two, that's still a very sound investment.
The web can be good for keeping up with rapidly changing libraries (Java's, for example). Then again, if your library is changing so fast that books on it are obsolete before they're useful, perhaps you should slow down. This problem is usually caused by adding too much to a library too fast, and the consequent continual efforts to clean up the mess.
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
I'm surprised this hasn't been mentioned yet. Godel, Escher and Basch by Douglas Hofstader. This is profound investigation into the fundamental theories that underly computer science. After reading this book everything else is just work. If you can understand Hofstader you have all the theoretical and philosophical underpinnings you need to really understand software.
The real joy is this book is not just meaningful it is also enormous fun. Hofstader covers some complex mathemetical ground (Turing machines, Cantorization, Godel's incompleteness theory) wrapped up in erudite and thought-provoking tales of the relationship of computer science, language, art and music.
Truly one of the great works of our field.
Sailing over the event horizon
- database design. Read Graeme Simsion's Data Modeling Essentials. This explains how to analyze proposed and existing business activities and accurately reflect them in a database schema. Knowing a lot about SQL or Oracle is not a substitute! A strong schema forces the database to do much of the work for you. A weak schema reduces the database to expensive passive storage.
- SQL. Read Joe Celko's SQL for Smarties. Work through the examples with Postgres or Oracle. (Knowledge is in the fingers.) Main benefit: the ability to craft a SELECT statement that generates a desired report with little or no postprocessing in the "host" language. On average, the database is going to be faster and less buggy at extracting, correlating and sorting data than any custom-written code. If you ever perform two SELECTs and knit the results together with custom code, your SQL knowledge may have room for improvement.
Geeks love introverted, clean, mathematical problems and hate ugly, fuzzy business-driven problems. That bias is reflected in the responses here - Knuth is the hands down favorite. While I don't dispute Knuth's value, the focus on algorithms reinforces the lamentable tendency to reinvent the database for each major application. The programmer with a knowledge of C and a head full of algorithms has in a sense a complete toolkit to take on the world, but the programmer with a high-level language and a relational database operates at higher leverage because he need not reinvent fundamental parts each time.For example, I learned many sorts in school. I have never used any of them at work. Perl has a built-in quicksort, and SQL has ORDER BY. I think you can assume that more energy and expertise went into Oracle's implementation of ORDER BY than you can bring to bear on average on a homemade sort.