Personal schedule for Julien Biezemans
Download or subscribe to Julien Biezemans's schedule.
David Chelimsky (DRW Trading),
Aslak Hellesøy (Bekk Consulting AS)
Average rating:
(3.75, 44 ratings)
Cucumber is all the rage these days, but many developers struggle to
understand how and when to use it. It is designed to be an Acceptance
Testing tool in the context of BDD, but that explanation tends to
bring up even more questions.
Read more.
Jeremy McAnally (Arcturo)
Average rating:
(1.76, 112 ratings)
This workshop will tour through a number of advanced, in-depth topics on Rails 3. We'll look take a tour of many of the new additions to Rails 3, talk about how to exploit Rails' new focus on Rack to your advantage, dig around in the source to really understand how many of the pieces work, and take a look at how to bring some common, advanced patterns used in Rails 2.x into the world of Rails 3.
Read more.
Michael Feathers (Obtiva, Working Effectively with Legacy Code)
Average rating:
(3.59, 112 ratings)
Keynote by Michael Feathers, Object Mentor.
Read more.
Joseph Wilk (Songkick.com)
Average rating:
(4.07, 44 ratings)
Tools like Cucumber encourage driving new pieces of functionality through tests which cut through the entire Rails web stack, including the database. As a consequence these Acceptance tests can be quite slow. This leaves us in a dichotomy, you want to keep adding new features to your product and you want to maintain rapid test feedback. Somethings got to give. So how do we scale Acceptance tests?
Read more.
Jesse Newland (GitHub)
Average rating:
(3.60, 20 ratings)
In order to ensure continuous application availability without dealing with antiquated monitoring tools a Rails developer should be able to assert the correct behavior of a production application from the outside in using familiar tools to protect revenue.
Read more.
Ian McFarland (Pivotal Labs, Inc.)
Average rating:
(4.59, 37 ratings)
In this presentation we'll share our insights into how to develop agile, robust, industrial strength code reliably and repeatably, through the application of our own flavor of XP-style agile development. We've been doing Agile for over 10 years, and Rails for over 4. We've delivered over 80 Rails apps to customers, and have learned a thing or two about how to do that sustainably and well.
Read more.
