The talk is based on observations and lessons learned from a few years of using South on large projects, with different teams and team makeups (mixes of developers, creative staff, etc.), and common questions on IRC / mailing list.

The demos will move quickly; a working understanding of creating and applying South migrations will be assumed. We'll make changes to a sample project, sometimes get ourselves into trouble, and pull back the curtains to figure out the best approach.

While going through the demos we'll take opportunities to learn how to consider:

• Impact on invidual developers
• Impact on other teammates / staff
• Impact on development and deployment environments
• Whether South can represent your desired operation in a sane manner
• Long-term code maintenance
• Testing changes and undoing messes

One thing I've found is that different teams and developers have varying philosophies about managing South migration histories over time. We'll put these ideas into context and audience members should come away with a good feeling about how to best use South for their particular needs.