saturnflyer

I had the benefit of working with rpwilcox in one of the trenches where I know I learned a lot. Very interested to read about his other experiences and learn more.

DCI has you split objects from their responsibilities until they are needed. This reduces your need to understad what eventually becomes (commonly in projects) massive classes with lots of responsibilities. But more so than that, in DCI you create a Context object whose responsibility is to coordinate objects and the roles they play: the Context represents your algorithm. This allows you to point to an object that is responsible for a business use case, rather than what is typically done by having methods strewn about the classes of you system with no indication of when they are needed.

Interesting. Maybe I'll rewrite that bit. Thanks for pointing that out.

I took that quote from that presentation. He hates all OO code, so it's not specifically Ruby that's the problem for him, but object orientation. His point, however, is that being able to reason about your program is important. That is also a driving factor behind DCI. OO programs often hide exactly what happens among objects because we mostly see everything from the perspective of a class, rather than a perspective of being among the communicating objects.

for you rodw, I shortened the width. It should be 970px now.

It's just been one of those things: wait to get it perfect or get it done. It's probably not great on a mobile phone either but I haven't had time to tackle that.

This book isn't an argument against documentation. Until the recent advent of DCI there was no programming paradigm that brought the algorithm to be a first class citizen. Tomdoc looks great, but it only describes methods or classes. Documentation will not tell you what will happen among a network objects during runtime, DCI will.

Clean Ruby is all about writing applications that are easy to understand by elevating the use case to a first class citizen. OO programs often split out methods and objects required for a use case like shrapnel. After reading Clean Ruby, you'll know how to bring them all together in one place to reveal your intent.

I've updated the text a bit and changed the signup button at the top to be a bit more obvious about it being a book. Thanks for the feedback!

Well, I'm not sure I do know what you mean. If you fill out the form, I'll email you with updates and eventually a discount code.

Thanks for the feedback. I'll clean up the text a bit then. Subscribers will get a discount on "Clean Ruby" when it's finished.

+1 app/models is for domain models