First faulkner I've read. Breathtaking at times, and then other times I got bored.
“She wants to pray, but she don’t know how to do that either.” "And h...moreFirst faulkner I've read. Breathtaking at times, and then other times I got bored.
“She wants to pray, but she don’t know how to do that either.” "And him being a kind of fierce little old man that a man wouldn’t cross without he thought about it first." "‘He don’t need any help,’ he thinks. ‘Not him. It’s hindrance he needs’;" "I imagine that after thirty years the machinery for hoping requires more than twenty-four hours to get started, to get into motion again."(less)
I highlighted a lot of this. Balanced, presents opposing views and acknowledges where own argument is weak. Very readable, including gems like "In fac...moreI highlighted a lot of this. Balanced, presents opposing views and acknowledges where own argument is weak. Very readable, including gems like "In fact, it was not the first time in history that it was the first time in history." Worth a read if you're into development.
Basic idea: "The technocratic approach ignores what this book will establish as the real cause of poverty—the unchecked power of the state against poor people without rights." "Morally neutral approaches to poverty do not exist. Any approach to development will either respect the rights of the poor or it will violate them. One cannot avoid this moral choice by appealing to “nonideological evidence-based policies” (a popular phrase in development today)." "King’s dream was that blacks would be able to say they were “free at last.” He did not first require an expert plan to make blacks “middle class at last.” "To a man in Uganda freedom just means “I do whatever I want with my cow.”
Entertaining jabs at technocrats: "The development audience gets excited about farmers in a remote but wired village finding out prices in real time for their crops. It fails to ask whether those farmers have motor vehicles to transport the crops to the market to get that price." "They promised to end poverty with broadband and they gave us young men watching porn."(less)
Recipes look quite good, though pretty American. Introduction is eager, informal, selective/sloppy with facts (or at least: doesn't provide enough con...moreRecipes look quite good, though pretty American. Introduction is eager, informal, selective/sloppy with facts (or at least: doesn't provide enough context to make claims believable - extraordinary claims, extraordinary evidence), does provide some good links to more information though.
Disclaimer: I just read "Should you eat meat?" which is the polar opposite style of this book, so I wasn't feeling particularly tolerant.
I have one friend with a personality who I think this book's style might appeal to, for the rest I need to find a different primer.(less)
Required reading for anyone running a small business. Or a large one probably. Skip over the personal bits, I give the author a pass for a recurring a...moreRequired reading for anyone running a small business. Or a large one probably. Skip over the personal bits, I give the author a pass for a recurring awkward dialogue between the himself and a female owner because it was written 20 years ago, the content is still relevant.(less)
If you are new to OO, this is a really good introduction. Useful examples, not preachy, discusses pros...moretl;dr you should read it if you're a programmer.
If you are new to OO, this is a really good introduction. Useful examples, not preachy, discusses pros and cons of different approaches.
If you are a veteran, this will give you concrete words to verbalize many things you already do, helping you to explain and teach others.
Things I particularly liked:
* Large number of examples, with specific explanations of each step. * "The purpose of design is to lower costs." If design or testing isn't doing that, it isn't doing what it should be doing. For example, on Law of Demeter: "as a "law" it's more like 'floss your teeth every day' than gravity". * Big focus on identifying things that change at different rates, and using that to influence your roles and public/private interfaces. * "Concrete is simple to understand, but hard to extend. More abstraction is harder to understand, but easier to extend." Then tension between these two is important. * Prefer template method over `super`, because it reduces dependency. (I hadn't considered doing this.) * Discussion of inheritance vs composition, and when to use either. (In general use composition, but inheritance is a better choice for certain things.) * The chapter on testing uses minitest with manual role verification. RSpec mocks can do this for you automatically*, but starting with doing it by hand is probably a better option so you can get a feel for what's going on under the hood. * Throughout she is very conscious of different needs and abilities of junior vs senior programmers. For example, well written tests reduce costs, but this is not true for many beginner programmers - they spend more time writing too many of the wrong kinds of tests, which end up making the program harder to change. She recommends sticking with it, most people make it through that phase ;)
A number of people at work have read it on my recommendation, and have all made a point of thanking me for it. (less)
Not usually a fan of collections of blog posts, but this works. There is enough glue and cohesion to make it read like a book - definitely a page turn...moreNot usually a fan of collections of blog posts, but this works. There is enough glue and cohesion to make it read like a book - definitely a page turner.
Everyone will get something out of this book (except maybe if you've devoured his blog) - lessons for being a CEO apply in virtually every endeavour, and it's much more real than a typical "business book".(less)