-
-
Replying to @erniemiller
@erniemiller@yaroslav criteria is: usage drives API, modules or classes organize the code base internally1 reply 0 retweets 0 likes -
Replying to @erniemiller
@erniemiller@yaroslav if the implementation is a mess that's bad quality, the surface in absolute terms is not very meaningful for us2 replies 0 retweets 0 likes -
Replying to @fxn
@fxn@erniemiller@yaroslav You can't honestly be saying that the complexity (and surface) of an active record model isn't causing pain.2 replies 0 retweets 0 likes -
Replying to @sgrif
@sgrif@erniemiller@yaroslav in Ruby, modules allow you to organize the code, delineate bolcks of functionality, and offer a convenient API5 replies 0 retweets 0 likes -
Replying to @fxn
@fxn@erniemiller Modules have the same problems as inheritance in general -- no explicit API, no privacy from collaborators1 reply 0 retweets 0 likes -
Replying to @erniemiller
@erniemiller@fxn Not to say all modules are bad all of the time. I think Enumerable is a great example of modules done right.1 reply 0 retweets 0 likes -
Replying to @sgrif
@sgrif@erniemiller Enumerable is the reuse use-case, code organization, responsability delineation, with no reuse, is another use case1 reply 0 retweets 0 likes
@fxn @erniemiller I strongly disagree, but I don't expect to be able to change your mind on this. Would love to chat more in not 140 chars.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.