freakish777 wrote:AI: A Modern Approach
This one is a bit advanced, but a fantastic book.
Head First: Design Patterns
This one is a bit basic, but a fantastic book. In fact more CompSci books need to be like this, instead of over complicating things, simplifying them to the point where anyone can pick it up, and have it make sense to them. Yes, there are some incredibly powerful things you can do the deeper your knowledge goes, but I'm sick of professors and authors of books saying any the following:
"Programming is complicated and hard to understand (and that's the way it should be)." No, it's as hard and complicated as you make it.
"You can't possibly program (or be a good programmer) until you first understand the underlying hardware, processor instructions, OS, history of computers (In My Day We didn't have hard drives! Everything was written to tape!), etc." Actually you can. Will you inevitably write a memory leak at some point? Sure. And when that happens, that's when you should start teaching students about how the underlying system is important, and considerations that have to be made to avoid making this error in the future.
"<Wall of text/speech, no parallels, allusions, comparisons or analogies given at all and expect you to understand>, congrats you're an expert now." Fuck. That. The concepts aren't hard to understand if you phrase them right. Stop phrasing them wrong.
Simon Shine wrote:Compilers: Principles, Techniques, and Tools (Aho, Sethi, Ullman)
cjmcjmcjmcjm wrote:If it can't be done in an 80x24 terminal, it's not worth doing
Meem1029 wrote:If you're looking for a fairly simple introduction to programming, <a href="http://htdp.org">How to Design Programs</a> is a pretty good book. It's what I learned with in high school and I believe is used at MIT for an introductory course.
Users browsing this forum: Fekeenuisance and 1 guest