by Ro Samour
by Bryan Liles
Everything you've done in your life has led you to where you are right now. All the good and bad decisions have helped make you the person that have evolved into. We all want to be good coders, and there are life lessons to be learned by observing others. Instead of letting you observing all my past failures and success, I'm going to recap them for you. From my troubled past to my current ruby undertakings; you'll get an eye of someone who laughs at MINSWAN every day.
As Ruby matures, understanding service oriented architecture is becoming more important for Rubyists to have in their toolboxes. This talk will focus on messaging systems in the SOA ecosystem, featuring a case study of an application that went from monolithic to service oriented, with messaging and queue systems driving the changes. Architecting, scaling, deploying, and maintaining messaging/queueing systems will be discussed, and tools developed along the way will be introduced.
This talk covers two powerful but incomplete artificial intelligence projects in Ruby: Archaeopteryx, a Ruby drum machine which can improvise its own rhythms, and Epic Towelie, which can automate several tasks involved in refactoring JavaScript, such as identifying duplication, identifying highly similar code, and extracting repetitive code into wrapper functions. The speaker may perform music; the speaker's code will definitely perform music. The talk will also pose an important and challenging question: do you need a goat to fly to the moon?
by Scott Parker and Dan Melnick
Most developers are familiar with the API driven architecture of Twitter, but few go so far as to develop their application the same way. By building a Great Wall between your business domain and the way users consume it, you separate your application into modular, isolated components with fewer interdependencies.
In this talk Dan Melnick and Scott Parker explore both the advantages and drawbacks of creating an application as a Sinatra API that is consumed by SproutCore. We'll also discuss alternative paths to incorporate an API driven architecture with a number of other frameworks.
Where is the "End of Men" in the Ruby community? Shouldn't the push for more paired-programming and team driven development encourage more women into the notoriously lone-wolf, up at all hours, "I'm better than a team" development community? So where are they? What percent of your software development team is women? Have you ever pair-programmed with a woman? This talk is going to ask some edgy questions about the Ruby community and who it's women are. I will be drawing parallels between my mountain climbing experiences and my experiences as a software developer.