6 ms·
Meh, I dunno. This list isn't really that great. It's good if your goal is to learn as many programming languages as you can, but it's sorely lacking fundamenta
by gfodor 16y ago
Meh, I dunno. This list isn't really that great. It's good if your goal is to learn as many programming languages as you can, but it's sorely lacking fundamentals. (Even considering the theory books, which are pretty all over the place.)
My list would definitely include more books around software architecture, system design, algorithms, data structures, and different domains of software like computer graphics, machine learning, databases, embedded systems, simulation/games, audio/video, and so on.
- krainboltgreene 16y agoThis isn't definitive, but it is focused on web development. Please suggest some books :)
- dboyd 16y agoThe Pragmatic Programmer: http://pragprog.com/titles/tpp/the-pragmatic-programmer http://pragprog.com/titles/tpp/the-pragmatic-programmer Code Complete: http://cc2e.com/ http://cc2e.com/ Introduction to Algorithms (google that one, it's hard to find a good link) Domain Driven Design: http://domaindrivendesign.org/books/evans_2003 http://domaindrivendesign.org/books/evans_2003 Design Patterns: Elements of Reusable Object-Oriented Software The term "web development" doesn't mean much. There is web design. There is application development. When the two mix, there is web application development. Any kind of application development is hard, and simply knowing a language or two isn't going to make you a good application developer any more than knowing english will make you Stephen King. (IMO)
- angrycoder 16y agoThose books are great, but they only start to make sense after you've been doing development for a few years. Its very hard to get any kind of 'buy in' with those when you are just getting started. I disagree that application development and web development are similar. When you build web apps like 'real' applications, you end up with all those heavy java frameworks. And god help your sanity if you ever been subjected to the code of a desktop application written by a web developer.
- StudyAnimal 16y agoI dunno about that. The bulk of an app should be business logic, or you are just plumbing / churning our boiler plate. Behind that theres some infrastructure, or connections to external systems, websites, file IO, hardware, databases. All that is not going to look much different, if you are doing it right. The only difference between a web app and a desktop app, is the presentation layer which should be as thin as possible, and whatever is hosting it, i.e. a framework, an executable. In fact most of the real apps I have been working on lately aren't one or the other, they are a mix. Basically a core of domain logic, with thin patches of external interface exposing it. A web page here, a web service there, a desktop app over there, a server here. And the line between is getting fuzzier. I hear some places are standardizing on technologies like Flex that can be either web apps or desktop apps depending on configuration. If I understand you correctly you are implying that web apps don't need to have as clean a design as desktop apps. I am not sure if that is what you mean, but if it is, then you are going have the same trouble with maintenance as a product matures if you ignore e.g. SOLID principles, separation of concerns etc, whether it is a desktop or web app. And you don't need any "heavy java frameworks" either. If anything web frameworks like rails encourage a cleaner design (ie via MVC) than typical desktop tools like what C# developers might use to make an app.
- tianyicui 16y agoThe good link for Introduction to Algorithms: http://mitpress.mit.edu/algorithms/ http://mitpress.mit.edu/algorithms/
- aaronblohowiak 16y agoStarting with Ruby is an interesting way to learn programming. I started with LOGO. I made that turtle DANCE! ;) Okay, well, maybe not. But it did give me a solid foundation that the computer is a robot that follows the commands. I fear that languages with too many features (objects? classes? blocks!?!?) confuse the heck out of the new programmer. My main objection to learning high-level languages first (or low level languages for that matter,) is that effectively debugging the language requires understanding concepts that are beyond your zone of proximal development.
- steveklabnik 16y agoWe put a LOGO dsl into Hackety Hack, which teaches with Ruby. https://github.com/hacketyhack/hacketyhack/blob/master/samples/Turtle%20Stars.rb https://github.com/hacketyhack/hacketyhack/blob/master/sampl...
- iuguy 16y agoI would agree. Some of the books I'd highly recommend for anyone looking to be a well-rounded hacker: * TCP/IP Illiustrated (Volumes 1,2 & 3) - W. Richard Stephens * The Web Application Hacker's Handbook - Stuttard, Pinto et al * The Shellcoder's Handbook - Kozoil, Aitel et al * The Cuckoo's Egg - Clifford Stoll * Neuromancer - William Gibson * ARM System-on-chip Architecture - Stephen B. Furber * Operating Systems Design & Implementation - Tanenbaum * The Design and Implementation of the FreeBSD Operating System - McKusick, Neville-Neil These are just a few, and I'm sure there's plenty of others, even better ones. But to truly round yourself out you need to know more than programming a few languages - you need to know the low-level end of things and the high-level view of the world.
- Seth_Kriticos 16y agoI'd add (from my bookshelf): * K&R: The C Programming Language (second edition) * Unix Power Tools * Advanced programming in the UNIX Environment (second edition) * OpenGL (Redbook, Bluebook, Superbible)
- iuguy 16y agoGood god yes, how could I forget Advance programming in the Unix environment. Awesome book.
- x0ner 16y agoI think your hacker definition falls a little more along the same lines as mine. I initially read the list expecting the author to be telling me ways of how to obtain 1337 skillz, but realized he was talking about hacking from the tinkering perspective. I really wish they would quit dicking with the definition. Crackers just sound so foolish.
- emzo 16y agoI know this is a very difficult question, but if you could choose only one book to convey the main ideas in each of those four areas you mention (software architecture, system design, algorithms, data structures), what would they be? I ask because I'm looking to buy some good books on the subjects.
- bnoordhuis 16y agoMy personal favourite is "Operating Systems: Design and implementation" by Tanenbaum, it covers all the subjects you mention.