Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Presentations Silos Are for Farmers: Production Deployments Using All Your Team

Silos Are for Farmers: Production Deployments Using All Your Team



Julian Simpson recommends practices to bring together development and operations, like: collaboration, don’t use email for internal communication, respect everyone, have lunch with the other team, discuss problems, joined retrospectives and stand-up meetings, co-locate sysadmins and developers, teach sysadmin to use VC, use CI and continues deployment, separate binaries and configuration files.


Julian Simpson started in technical support and has been a Unix system administrator for many years. After running his own business connecting people to the Internet, he worked on large software builds, continuous integration and deployment at ThoughtWorks for 4 years. Currently, he is working for a media company doing build and release management and production system 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.

Recorded at:

Jun 14, 2010

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Lots of sound advices for developers and sysadmins alike

    by Olivier Gourment,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    For anyone considering watching this, GO AHEAD. It might look like more time is spent on each slide than required, but it actually leaves some time to think about each advice and why they make sense and how to go about implementing them in your organization. I highly recommend this talk.

    One note about whoever works in financial institutions. I still think that all advices apply here as well. For example, manual checks on code changes deployed do not need to happen before EACH deployment, or even before each deployment to PRODUCTION necessarily: if the code promotion process is properly automated with the right privileges and restrictions (code cannot be changed from one environment to the next).

    PS: Not sure why there are less comments on InfoQ presentations as there used to be.. Any idea?

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p