Timeline for Why do people use programming books?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 9, 2011 at 5:55 | comment | added | Jared Updike | +1 for " it covers material that, while not actually necessary, will help you later" -- good programmers have a deep well of knowledge to draw on. Even if you don't remember all the details, but you know the thread to tug on and learn it when you need it, it can be quite invaluable! | |
| Jul 29, 2011 at 1:30 | history | edited | Peter Mortensen | CC BY-SA 3.0 |
added 80 characters in body
|
| Jul 28, 2011 at 15:09 | history | made wiki | Post Made Community Wiki by Mild Fuzz | ||
| Jul 28, 2011 at 13:12 | comment | added | rlperez | Definitely appreciate the mention on styles, practices, and patterns. These are the books that are really the beneficial ones. You can learn to program by just having a problem to solve and solving it. You learn to program well by learning styles, practices, and patterns. Still, the best place to get a comprehensive understanding of these concepts are texts. | |
| Jul 28, 2011 at 7:49 | comment | added | Péter Török | +1 for mentioning what I would have written: that the "best practice / methodology" type of books differ greatly from the "how to do X using Y" kind of books. And the former are the really valuable stuff, because it teaches hard-earned general problem-solving experience. Once you learn unit testing, refactoring, estimation etc., you can apply and adapt it to a host of languages / domains / projects. | |
| Jul 28, 2011 at 6:29 | history | answered | thorsten müller | CC BY-SA 3.0 |