And 3) A/B'ing real code against proposed methods and architectures 
-
-
that’s the thing man, your basecamp-as-a-metric approach hurts rails, this is no longer 2005
9 replies 0 retweets 7 likes -
If people aren't measuring their perspective against real code, which means their app, we lose our bearings quick.
2 replies 1 retweet 14 likes -
people really really underestimate this. Reality matters a lot (obvious in retrospect right?)
2 replies 1 retweet 3 likes -
well, thousands of people have really bad reality bkz of poor design choices in Rails. Really matters a lot too :)
1 reply 0 retweets 0 likes -
yeah, and I took that reality and helped to change rails in rails3, which matters too! But you're grumpy :)
1 reply 0 retweets 1 like -
rails 3 illustrates that engaging
@dhh on the issue of modularity works well if you're willing to do the work.3 replies 0 retweets 2 likes -
good to know, then I hope AR will be modularized more in the future :) (not talking about ruby modules)
2 replies 0 retweets 0 likes -
you don't need to tell me that modularity is not Ruby modules ;) http://yehudakatz.com/2008/11/15/mythbusting-rails-is-not-a-monolith/ …
1 reply 0 retweets 1 like -
Replying to @wycats
just trying to avoid any more confusion (ie other people are probably reading this thread)
1 reply 0 retweets 0 likes
np. btw if you read that post you'll see that we actually addressed most of the "big" modularity issues from that timeframe
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.