InfoQ

InfoQ

Presentation

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Recorded at:
Recorded at

Rails in the Large: How Agility Allows Us to Build One Of the World's Biggest Rails Apps

Presented by Neal Ford on Mar 12, 2010 Length 01:08:47     Download: MP3
Sections
Development,
Architecture & Design
Topics
Performance & Scalability ,
Dynamic Languages ,
Ruby on Rails ,
Ruby
Tags
Rails ,
Scalability ,
Ruby on Rails ,
Performance Tuning
 

How would you like to view the presentation?

In case you are having issues watching this video, please follow these simple steps to help us investigate the issue:
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
Summary
Neal Ford shows what ThoughtWorks learned from scaling Rails development: infrastructure, testing, messaging, optimization, performance.

Bio
Neal Ford is Software Architect and Meme Wrangler at ThoughtWorks, a global IT consultancy with an exclusive focus on end-to-end software development and delivery. He is the designer/developer of applications, instructional materials, magazine articles, courseware, video/DVD presentations, and author and/or editor of 5 books.

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.
TW sucks by Christopher Churchill Posted
Re: TW sucks by Russell Leggett Posted
Re: TW sucks by Christopher Churchill Posted
Comfortable workspace? by Hermann Schmidt Posted
Re: Comfortable workspace? by Ryan Slobojan Posted
  1. Back to top

    TW sucks

    by Christopher Churchill

    The fun stuff sucked. Also the "No emails" while working really sucked as well. An employer should not control that. Its the motivation of the employee.

  2. Back to top

    Re: TW sucks

    by Russell Leggett

    Are you speaking as somebody who worked on this project?

  3. Back to top

    Re: TW sucks

    by Christopher Churchill

    No

  4. Back to top

    Comfortable workspace?

    by Hermann Schmidt

    Very inspiring talk - in the technical domain.

    However, with all respect, the workspace in this project is TERRIBLE! 40 people crammed into a room, each with less than 1 meter distance to his neighbour. Background music you cannot escape from, like in a supermarket? The blinds are down and the artificial light is on! Why? Apparently because the projections would otherwise not be readable.

    You can't be serious.

    The submarine comparison is quite valid. But what is so terrific about working in a sub? It is one of the worst places to be that I can imagine.

    It is no surprise to me that Neil emphasized "fun stuff" so often, because the fun is not apparent at all, at least for me. I can't be fun working in a chicken farm like this 10 hours a day. The silly Starbucks cup thing looks more like a desperate attempt to me.

    Answer yourself a simple question: can you imagine spending your professional life (yes, that's 30 years and more) in such an environment? I bet you don't!

  5. Back to top

    Re: Comfortable workspace?

    by Ryan Slobojan

    Hi Christopher,

    Your comment was deleted because it added little to the discussion, and it was in a very negative (non-constructive) tone. Please feel free to find a way to express what you were trying to say again, but in a constructive manner - your previous comment appeared to be a series of potshots with nothing else of benefit, and which was only very loosely related to the discussion in this thread.

    Thanks,

    Ryan Slobojan
    Chief Editor, InfoQ.com

Educational Content

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.

Max Protect: Scalability and Caching at ESPN.com

Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.

The Seven Deadly Sins of Enterprise Agile Adoption

Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.

Questions for an Enterprise Architect

Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?

Wrap Your SQL Head Around Riak MapReduce

Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.