BEGIN:VCALENDAR
X-WR-CALNAME:RailsConf 2011
VERSION:2.0
PRODID:Expectnation
CALSCALE:GREGORIAN
BEGIN:VEVENT
DTEND;TZID=US/Eastern:20110518T113500
DTSTART;TZID=US/Eastern:20110518T104500
DTSTAMP:20110917T172741
LOCATION:Ballroom III
URL:http://en.oreilly.com/rails2011/public/schedule/detail/19424
UID:http://railsconf.com/--s2011-05-18-10:45--19424
SUMMARY:Beyond MVC -- DCI
DESCRIPTION:Presented by Mike Dietz (ThoughtWorks). MVC inventor Trygve 
 Reemskaug and James Coplien have a new vision for software, called DCI -
 - Data, Context, and Interaction.  Although as conceptually elegant as M
 VC, and with the same potential to improve software, DCI's innovations a
 re not easily implemented in Java or C#.  That is not the case with Ruby
 , however, which puts Rails developers in a unique position to lead the 
 way.
END:VEVENT
BEGIN:VEVENT
DTEND;TZID=US/Eastern:20110518T123500
DTSTART;TZID=US/Eastern:20110518T114500
DTSTAMP:20110530T192729
LOCATION:Ballroom IV
URL:http://en.oreilly.com/rails2011/public/schedule/detail/19337
UID:http://railsconf.com/--s2011-05-18-11:45--19337
SUMMARY:Why Can't I Test My JavaScript?
DESCRIPTION:Presented by Greg Moeck (Strobe, Inc.). The Ruby/Rails commu
 nity is known for it's adoption of TDD,  yet that seems to stop at the b
 order that is our web browsers. The issue isn't testing tools, the brows
 er or the DOM. It's us. We write untestable JavaScript and our tests are
  yelling at us, begging us to change. Will we listen? Come and learn how
  we can push the Ruby testing philosophy into JavaScript, and impact the
  apps of the future.
END:VEVENT
BEGIN:VEVENT
DTEND;TZID=US/Eastern:20110518T144000
DTSTART;TZID=US/Eastern:20110518T135000
DTSTAMP:20110620T184938
LOCATION:Ballroom IV
URL:http://en.oreilly.com/rails2011/public/schedule/detail/19458
UID:http://railsconf.com/--s2011-05-18-13:50--19458
SUMMARY:Test Your Legacy Code
DESCRIPTION:Presented by Noel Rappin (Obtiva). Everybody wants to do tes
 t-driven development, but switching to TDD or BDD on an existing project
  that doesn’t have tests presents special challenges. This session will 
 show you how to work around dependencies that make testing legacy code s
 o complicated. Topics include using Cucumber for black-box testing, usin
 g mock objects to limit dependencies, and using Ruby dynamism to cut thr
 ough problems.
END:VEVENT
BEGIN:VEVENT
DTEND;TZID=US/Eastern:20110518T154000
DTSTART;TZID=US/Eastern:20110518T145000
DTSTAMP:20110525T105226
LOCATION:Ballroom II
URL:http://en.oreilly.com/rails2011/public/schedule/detail/17700
UID:http://railsconf.com/--s2011-05-18-14:50--17700
SUMMARY:When and How to Expose Services
DESCRIPTION:Presented by Jamis Buck (37signals), Jeffrey Hardy (37signal
 s). Drawing from the authors' own experiences, methods and guidelines wi
 ll be presented for exposing and sharing services within and between lar
 ge Rails-based systems.
END:VEVENT
END:VCALENDAR
