rcmnd

Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment AutomationBook

by Jez Humble and David Farley

Who uses, recommends or left Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation, in their own words: each a verbatim quote with a link to where it was said.

1 person

Software design writer and chief scientist at Thoughtworks; wrote Refactoring and Patterns of Enterprise Application Architecture.
loved

It seems to me that a book that can show you how to deliver your software frequently and without the usual stresses is a no-brainer to read. For your team's sake, I hope you agree.

Fowler's notes on Continuous Delivery, one of the books in his Signature Series.

2010-01-01·martinfowler.com ↗

Every entry is a verbatim quote and a link to the public post it came from. Nothing is paraphrased. If it is not on record somewhere public, it is not here.

The verdict is what they actually said: loved and liked are explicit; recommended means they told others to get it; uses means they only say they use it; read is a book on their public shelf with no verdict; mixed and disliked are kept too.

A dashed affiliate link, sponsored or their own label means the post disclosed a relationship. It is shown, never hidden.

The shading behind a date shows how dated a recommendation is for its kind of thing.

The shading behind a date shows how dated a recommendation is, for its kind of thing. Fully green is recent. It drains a quarter at a time as the post gets older, and is empty once it reads as dated.

What counts as old depends on the thing. A laptop praised four years ago has been replaced twice; a book loved twenty years ago is probably still loved. The shading is gone after about:

Stripes mean the post carries no date and the date shown is an estimate. No date at all, no shading.