Object Oriented Design
We're kicking off an occasional set of discussion/study sessions exploring best practices (using Ruby, but applicable elsewhere).
What makes a good object oriented design? What is "good-enough"? What compromises do you (must you?) make in production systems?
Part book review/study group, part war stories, part coding exercise, we'll be spending time in this and other sessions discussing SOLID principles (as coined by Michael Feathers and further discussed by Robert Martin).
We'll use Sandi Metz's "Practical Object Oriented Design in Ruby" as our text. Read Chapter 1-3.
I recommend picking up a paper or ebook copy from Amazon or other digital book provider: http://www.amazon.com/Practical-Object-Oriented-Design-Ruby-Addison-Wesley/dp/0321721330
Go to Attendee List