The document discusses best practices for developing large-scale Ruby on Rails applications. It emphasizes the importance of prioritizing performance and stability over new features by avoiding complexity, designing for caching, and using simple SQL queries. It also covers practices like continuous integration testing, remote testing, exception monitoring, feature flagging for prototypes, and automated deployment processes.
97. How did using a CI change our development flow?
Only release successful CI builds
Test coverage as a requirement
Tests should be written so they can run on a CI
2011 7 19
99. $
cap
production
deploy
Add a "deploy message" to every release
(ex: "Added feature x", "Fixed bug z" etc)
Skype notification
Mail sent to developer and support mailing lists
2011 7 19
107. Expands upon Rails functionality
Selective release of new features
(ex: “Show feature X only to users A, B, C)
Used for prototyping
Specs not required
If an exception occurs in an extension, it is turned off automatically
2011 7 19