I enjoyed the thorough explanation. Thank you.

> Also note that a class with 10+ instance methods is likely a smell that it is doing too much, and that it should be refactored out to multiple coordinator classes (classes that work together, but each are small enough to be simple to generate and test).

Please allow me provide some context about the example class with 10+ instance methods.  

I'm ultimately interested in writing API wrappers, so I have been studying Tim Case's [Echowrap Gem](https://github.com/timcase/echowrap/tree/master/lib/echowrap).  His [artist](https://github.com/timcase/echowrap/blob/master/lib/echowrap/api/artist.rb) class has 10+ instance methods, but they are all [tested](https://github.com/timcase/echowrap/blob/master/spec/echonest/api/artist_spec.rb) using before filters to instantiate a client or stub a get request for each example test. 

As I let this all sink in, all of this reminds me of English class -- there's no one "right way" to write an essay because every essay's purpose and topic is different, as well as the writer's respective style. Same with writing code specs. 

Looking forward to the next video!