Ask HN: Best books under 200 pages for developers?
31–40 of 106 posts
Re: Ask HN: Best books under 200 pages for developers?
#32Re: Ask HN: Best books under 200 pages for developers?
#33Re: Ask HN: Best books under 200 pages for developers?
#34A Philosophy of Software Design. Very well-written. At 190 pages, quite likely finish-able in a weekend. But if you get 70% of the way through it, that is still very valuable. It makes sense as an underlying set of principles that explain why you would use design patterns.
Re: Ask HN: Best books under 200 pages for developers?
#35A Philosophy of Software Design. Very well-written. At 190 pages, quite likely finish-able in a weekend. But if you get 70% of the way through it, that is still very valuable. It makes sense as an underlying set of principles that explain why you would use design patterns.
Beyond his credibility as the creator of Tcl, in the talk he gave at Google about the book [1] he describes the course he teaches that was the inspiration for the book. The course is to write a word processor with a team and extended it with features over the semester, swapping codebases between teams so occasionally you have to work with other's code. Essentially the largest possible code project you can fit in one semester. Along the way, Ousterhout will give a deep code review of the each project. I think it must be very insightful to see the same project implemented so many ways, and to see what works in terms of simplicity and extensibility.
Re: Ask HN: Best books under 200 pages for developers?
#36Re: Ask HN: Best books under 200 pages for developers?
#37Finally picked up Strunk and White after years of procrastination and so far it has been a tour-de-force consolidating/spelling out the knowledge I picked up along the way (ESL). I found mentally swapping out words about writing for words about programming to be fun.
Re: Ask HN: Best books under 200 pages for developers?
#38Re: Ask HN: Best books under 200 pages for developers?
#39Re: Ask HN: Best books under 200 pages for developers?
#40A Philosophy of Software Design. Very well-written. At 190 pages, quite likely finish-able in a weekend. But if you get 70% of the way through it, that is still very valuable. It makes sense as an underlying set of principles that explain why you would use design patterns.