Rails in the Large: How Agility Allows Us to Build One Of the World's Biggest Rails Apps
Neal Ford shows what ThoughtWorks learned from scaling Rails development: infrastructure, testing, messaging, optimization, performance.
Presentation
Recorded at:
CI from the Trenches: Real-World Continuous Integration Challenges (and what to do about them)
Presented by Julian Simpson on Oct 12, 2009
- Community
- Agile
- Topics
- Agile Techniques
- Tags
- QCon ,
- Continuous Integration ,
- QCon London 2009
-
- The next QCon is in London Mar 10-12, Join us!
Summary
Many organizations will tell you that they are "doing" continuous integration. A boat anchor of a PC in the corner running an old version of CruiseControl might tick a few boxes, but is it really effective? As we get better at CI, we should see our feedback loop extend out past development. But what strategies do we have for doing this and keeping the feedback loop tight for the developers?
Bio
Julian Simpson started his career in technical support. He has run his own business connecting people to the Internet, been a Unix systems administrator. Julian spent four years at ThoughtWorks doing build, continuous integration and deployment on large software projects. Presently he is working at a media company doing a mix of build and release management and production systems administration.
About the conference
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community. QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
Many organizations will tell you that they are "doing" continuous integration. A boat anchor of a PC in the corner running an old version of CruiseControl might tick a few boxes, but is it really effective? As we get better at CI, we should see our feedback loop extend out past development. But what strategies do we have for doing this and keeping the feedback loop tight for the developers?
Bio
Julian Simpson started his career in technical support. He has run his own business connecting people to the Internet, been a Unix systems administrator. Julian spent four years at ThoughtWorks doing build, continuous integration and deployment on large software projects. Presently he is working at a media company doing a mix of build and release management and production systems administration.
About the conference
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community. QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
RelatedVendorContent
Agile Development: A Manager's Roadmap for Success
Agile Development e-Kit: Educational Content from Rational
Related Sponsor
VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.
- This article is part of a featured topic series on QCon
- See more QCon content at: http://www.infoq.com/qcon
- Other recent content items in this topic
No comments
Watch Thread Reply