Did DHH actually agree to do this before you guys built this? One thing that is not clear from your site, that I think should be, is that the code discussions need to happen over unconventional Rails design patterns. DHH was saying he was willing to ping pong on the original discussion thread over a design pattern in a submitted article that he thought was an unnecessary abstraction.
I don't entirely know what's going on here, but I looked at the linked thread and dhh says twice that he would love to do code ping-pong.
DHH Ping Pong
11–20 of 21 posts
Re: DHH Ping Pong
#12Is this some passive aggressive shit?
"If this is a poor example, pick a good example. I'll be happy to code ping pong you whatever example you choose." -DHH
HN comments are not exactly the best place to review code side by side. I'm glad he is participating and I'm looking forward to the comparisons
Re: DHH Ping Pong
#13Is this some passive aggressive shit?
Re: DHH Ping Pong
#14This is really funny. Hope he's on board.
Re: DHH Ping Pong
#15Are you just collecting gist submissions, or are you planning to provide some discussion infrastructure? If it's the latter, perhaps make it more open-ended so it can be used by everyone for reviews?
On my team, when we are sketching out new infastructure, we'll fork each other's gists, which while good, could probably be more elegant since the fork experience isn't as powerful in Gists as it is in Github compare view. Perhaps this is the beginning to a cool project for that. Would rather have a ping pong game though.
Re: DHH Ping Pong
#16Most of the designs that DHH doesn't like are from complicated applications that need to deviate from The Rails Way.
I built my e-commerce business with Rails/ActiveRecord back in 2006, when rails was at version 0.7.
For the first few years, I followed rails conventions religiously. There's a point where you have to outgrow them. And that legacy approach is a major pain now. Having a class that wraps a database table and contains all the functionality that accesses that table doesn't scale at a certain point.
But I'm not going to try to show those pains in under a couple hundred lines of code that someone can understand in an hour. Anything that can be compressed to that point doesn't need a complicated design.
Re: DHH Ping Pong
#17Under 80 lines is a problem. Most of the designs that DHH doesn't like are from complicated applications that need to deviate from The Rails Way. I built my e-commerce business with Rails/ActiveRecord back in 2006, when rails was at version 0.7. For the first few years, I followed rails conventions religiously. There's a point where you have to outgrow them. And that legacy approach is a major pain now. Having a clas…
Re: DHH Ping Pong
#18Did DHH actually agree to do this before you guys built this? One thing that is not clear from your site, that I think should be, is that the code discussions need to happen over unconventional Rails design patterns. DHH was saying he was willing to ping pong on the original discussion thread over a design pattern in a submitted article that he thought was an unnecessary abstraction.
Re: DHH Ping Pong
#19Is this some passive aggressive shit?
Re: DHH Ping Pong
#20Are you just collecting gist submissions, or are you planning to provide some discussion infrastructure? If it's the latter, perhaps make it more open-ended so it can be used by everyone for reviews?
Would that work as a basic infrastructure for discussion? Otherwise - how would you see it?