Close and Go BackBack to Viget

The Hoedown Wrap-up

Ben Scofield
Ben Scofield, Development Director, August 12, 2007 2

Patrick, Clinton, and I spent Friday and Saturday with 100+ other Ruby developers at the Ruby Hoedown here in North Carolina, and we had a great time. The sessions ranged from conceptual (Ken Auer talked about “Crossing the Chasm,” pulling examples from the history of Smalltalk) to highly technical (Jared Richardson showed just how easy it is to turbocharge your Ruby by dropping down into C), and, as so often happens, meeting the other attendees was tremendously valuable in and of itself.

I think the sessions we got the most out of were the opening workshop on testing (which raised over $3,000 for charity), the lightning talks on the second day (where nearly a dozen attendees, including Clinton and Patrick, spent 5 minutes each presenting things they’ve been working on), and Marcel Molina‘s closing keynote on code beauty (which was easily the most thought-provoking event of the conference), but all of the sessions had something to offer.

One other thing of note came out of the Hoedown - lunch on the second day provided the opportunity for people interested in individual topics to come together in Birds of a Feather sessions. One of these BoF sessions (on using Ruby to enact social change) has resulted in the creation of a new rubyforchange project on Rubyforge. This project, with its accompanying mailing list, will serve as a focus for Ruby developers who want to use their skills to benefit others. It’s heartening to see that the community is continuing to make a concerted effort to give back.

Finally, I’d like to say that Nathaniel and Jeremy did a fantastic job putting this on, and we can’t wait ‘til next year!

Trackback: As expected, BarCampDC was indeed sweet on 08/12 at 08:00 PM [...] can read some other good conversation about BarCamp at Russell Heimlich’s blog, the Viget Blog, and many other sites. And you can find hundreds of pictures on flickr. See you all next [...]----- [...] In addition to Jackson and Andy, we had Thanny, Rob, Erik, Jim, and Trace from Viget there too.  Trace gave a talk on Google Analytics, Thanny and Rob coordinated a discussion around design process, and Jackson did one on mobile web (in addition to being the MC).  Had the the Ruby Hoedown (also this weekend, also sponsored by Viget) down in North Carolina not attracted most of our development group, they would have been there talking about Rails in a heartbeat.  Check out Ben’s recap of that event. [...]-----
Clinton R. Nixon said on 08/13 at 09:07 AM

The Ruby Hoedown was indeed thought-provoking. One thing I liked about this conference is the speakers’ willingness to be assertive and bold in their statements. Any conference where I disagree with speakers as much as I agree is one I’ll think about for a long time.

I’m very glad to see the Triangle becoming a hot spot for Ruby development, and really proud to be a part of that.

Patrick Reagan - Director, Application Development said on 08/14 at 09:25 AM

I’ll echo the sentiments of both Ben and Clinton - it’s always great to connect with the Ruby community at these events and see both familiar faces and new ideas.

The lightning talk format was perfectly suited for me to demo Tyrant, our open-source “meta” Rails application.  I’m looking forward to polishing things up a bit for a demo at the upcoming Lone Star Ruby Conference.

Trackback URL: Trackbacks are disabled for this entry

Comments for this entry were closed after 60 days.

A Development Community for Viget Labs and Beyond

Every team member here at Viget Labs strives to be an innovator. We members of the development team are no different - that's why we're constantly engaging in community discussions and exploring the unknown that is the next generation of open-source web applications.

Viget Is Hiring!

Viget has job openings for Ruby Developers, Interns, and Front-End Developers. Learn More »

Recent Comments

I think that polymorphic_url(@commentable, :anchor => “comment_#{@comment.id}") should work. You can also refactor the “comment_#{@comment.id}” to a separated method, like dom_id, which returns the dom identifier of the comment.