Difference between revisions of "Continuous rewriting"
From CitconWiki
Jump to navigationJump to search (first draft of chart) |
(chart finished) |
||
| Line 18: | Line 18: | ||
|- | |- | ||
! scope="row"| Continuous Deployment | ! scope="row"| Continuous Deployment | ||
| − | | | + | | |
| − | | | + | | |
| − | | | + | | ''Delivery hurts, so automate & do more often.'' - one-click deploy, IMVU |
| − | | | + | | Tools and culture! - DevOps, Puppet, Chef, Capistrano, Octopus |
| − | | | + | | General adoption by advanced teams? - CD book |
|- | |- | ||
! scope="row" | Continuous Rewriting | ! scope="row" | Continuous Rewriting | ||
| − | | | + | | |
| − | | | + | | |
| − | | | + | | |
| − | | | + | | ''Rewrites hurt, so automate & do more often.'' - DRW (Dan North), Forward (Fred George) |
| − | | | + | | ???? |
|} | |} | ||
Revision as of 12:53, 8 November 2012
Squirrel presented for discussion the thesis that "Continuous Rewriting" is an emerging theme for software development, a successor to better-known ideas "Continuous Integration" and "Continuous Deployment". The session opened with discussion of this chart:
| 2000-3 | 2004-6 | 2007-9 | 2010-12 | 2012- | |
|---|---|---|---|---|---|
| Continuous Integration | Integration hurts, so automate & do more often. - Daily Builds, Ant, CruiseControl | More tools! - JetBrains, Hudson, BuildForge | Adopted by advanced teams - CI books, CITCON | Tool shakeout, standard for new teams - Jenkins | Adopted by late majority? |
| Continuous Deployment | Delivery hurts, so automate & do more often. - one-click deploy, IMVU | Tools and culture! - DevOps, Puppet, Chef, Capistrano, Octopus | General adoption by advanced teams? - CD book | ||
| Continuous Rewriting | Rewrites hurt, so automate & do more often. - DRW (Dan North), Forward (Fred George) | ???? |
