Скачать с ютуб Practical Object Oriented Design in Ruby - Panel 1 в хорошем качестве

Practical Object Oriented Design in Ruby - Panel 1

INTROS Ezra 01:55 - Why did you choose the chapter on single responsibility principles? 03:13 - Describes Single Responsibility 05:23 - How do I use single responsibility principles? JJ 08:47 - Why did you choose the chapter on dependency injections Oscar 11:33 - Why did you choose the chapter on inheritance? Joe 13:39 - Why is POODR so influential and what other books/resources are available? Questions 15:29 - Why is the single responsibility principle important? 17:07 - What do they say about optional parameter methods for single principle? 20:43 - What makes a good candidate for an inheritance hierarchy? 22:56 - Ruby gives us a bunch of options like type of object, Is a type? Has a type? When do you use modules and mixin with inheritance? 26:26 - Follow up question Inheritance vs Composition? 29:38 - How do you make the distinction between coding for the future or keeping your code well factored? 31:56 - How does test driven development highlight too many dependencies? 34:56 - Define Inheritance vs Composition? 43:37 - Does the book talk about threads? - No but Joe provides other resources/books 45:46 - Any good success stories of getting a group of people to write good code? 49:17 - How do you recognize dependencies in code and are there any tools to quantify those dependencies? 53:25 - Talk to us about your favorite books on software design?