Comments on Thomas Ferris Nicolaisen's blog: Why Releasing More Frequently is Good For You

@Gin: Thanks for commenting! My thoughts are very ...

2011-11-14T20:31:47.287+01:00

@Gin: Thanks for commenting! My thoughts are very influenced by Beck, so that figures :)

Great thoughts. Somewhat reminds me to the influen...

2011-11-14T18:57:58.568+01:00

Great thoughts. Somewhat reminds me to the influence diagrams found at the end of Kent Beck's good old TDD book.
It looked something like more frequent tests -> more _confidence_ -> productivity.

This looks the same, more fundamental principle ('test' generalised as 'feedback'). Apart from the link mentioned above (frequent releases forces you to automate things better, which in turn is a positive feedback loop on both frequent releases and performance directly), it seems to help eliminate the other hindrance against itself. That is, I found a common reason for not making a release is lack of confidence in stability/code maturity - which this loop helps with: frequent feedback -> confidence -> performance.

@Patrick: Thanks for the comment! Good point. Ther...

2011-10-04T23:23:53.617+02:00

@Patrick: Thanks for the comment! Good point. There could be another bubble above Safety called Process or Routines that apply to the stability of doing releases. Releasing frequently feeds directly back there, like you say.

Also releasing frequently minimizes the stress of ...

2011-10-04T15:12:39.729+02:00

Also releasing frequently minimizes the stress of deployment, because to be able to release (and deploy) often, you need good automation and a clean process, which is well understood by doing it on a regular basis instead of once a quarter or worse.