I work for a company where our "suite" consists of 3 large components: a back-end system, a web-app, and software installed to the devices.
The back-end systems guy read mostly Java, JavaEE, EJB3.x (the better one of course), JMX, PostgreSQL (admin, performance, the usual drill) and everything that DHH mentioned.
The software/firmware/hardware guys are reading what you listed above (including Advanced Programming in the UNIX Environments, UNIX Network Programming vol 1-2, Windows Internals, etc).
I do think there is a "generational" (used loosely, as the generations here are much shorter than what we usually think of in terms of generations) component to it as well, just in the sense that what you consider the "software/firmware/hardware" guys were much closer to being the entire set of developers up until the early to mid 1990s than they are now. The concerns of today's embedded developer were the concerns of virtually everyone back then.
As a 39 year old, my list is virtually identical to jijji's and most people I know who program and who are about the same age or older would almost certainly cite a huge overlap if not the exact same list.
I like that you included a Richard Stevens book. He is underrated IMO. I own 3 of his books.. pretty much taught me C. He really knows how to explain C in a clear, easy to understand way. Great for beginners who want to learn.
I think you meant The C Programming Language by Brian Kernighan and Dennis Ritchie.
Unless there is another C Programming Language book that I am not aware of...
Comments
I guess I grew up in a different time:
* The C Programming Language by Dennis Kernighan and Brian Ritchie
* Expert C Programming: Deep C Secrets by Peter Van Linden
* TCP/IP Illustrated Volume I: The Protocols by W. Richard Stevens
* The UNIX System by S.R.Bourne
* The Algorithm Design Manual by Steve S. Skiena
Nah, just different domains that's all.
I work for a company where our "suite" consists of 3 large components: a back-end system, a web-app, and software installed to the devices.
The back-end systems guy read mostly Java, JavaEE, EJB3.x (the better one of course), JMX, PostgreSQL (admin, performance, the usual drill) and everything that DHH mentioned.
The web-app guys read mostly front-end stuff (JS, Backbone, Underscore, MVVM/MVC/MVP technique, CSS spriting, YUI compressors).
The software/firmware/hardware guys are reading what you listed above (including Advanced Programming in the UNIX Environments, UNIX Network Programming vol 1-2, Windows Internals, etc).
Still relevant :)
I do think there is a "generational" (used loosely, as the generations here are much shorter than what we usually think of in terms of generations) component to it as well, just in the sense that what you consider the "software/firmware/hardware" guys were much closer to being the entire set of developers up until the early to mid 1990s than they are now. The concerns of today's embedded developer were the concerns of virtually everyone back then.
As a 39 year old, my list is virtually identical to jijji's and most people I know who program and who are about the same age or older would almost certainly cite a huge overlap if not the exact same list.
I agree.
When I read this list, my first thought was "I know exactly when you started programming, and the types of apps you were writing".
I like that you included a Richard Stevens book. He is underrated IMO. I own 3 of his books.. pretty much taught me C. He really knows how to explain C in a clear, easy to understand way. Great for beginners who want to learn.
I think you meant The C Programming Language by Brian Kernighan and Dennis Ritchie. Unless there is another C Programming Language book that I am not aware of...
Great list.
The Peter Van Linden's book is the most fun and engaging programming book I've ever read (despite being a bit dated at the time I read it).
I know that feeling :) It actually made me interested in participate in the International Obfuscated C Code Contest. http://www.ioccc.org/
Is The Unix System still relevant now?
It's just a good book written by one of the founders, and offers unique insight into the design and implementation of *nix systems.