Continuous Delivery and DevOps

What Hacker News says

1. RandomSortOct 2018
   In Continuous Delivery and DevOps:

   Lean software Development - Mary & Tom Poppendieck

   The DevOps Handbook - Gene Kim, Jez Humble, Patrick Debois

   Accelerate - Nicole Forsgren, Jez Humble, Gene Kim

   Continuous Integration - Paul M. Duvall, Andrew Glover, Steve Matyas

   Continuous Delivery - Jez Humble, David Farley

   Show morethread
2. sciurusApr 2017
   You may like Build Quality In.

   "The interdependent disciplines of Continuous Delivery and DevOps are of immense value to an organisation, but they are hard. We have seen Continuous Delivery and DevOps work in the wild, as have other practitioners. We want to help people on their own Continuous Delivery and DevOps journey, by sharing the experiences of those who have done it – what worked, what didn’t, and the highs and lows of trying to build quality into an organisation."

   https://leanpub.com/buildqualityin

   Show morethread
3. 1337shadowAug 2019
   "DevOps" used to be a methodology where a Dev and an Ops share a same goal of delivering value into production, at least, that's in the book I have read.

   A sort of extension of the Lean System where workers from different areas share a common goal of delivering value to the final customer (in production), the same card may require a backend dev, frontend dev, and an ops to share the goal to take this card from idea to production, and then monitoring how it behaves in production.

   For people who have not read the same books, "DevOps" mean things like "applying dev method in the operation field" ie. with ansible and the likes, coding the infra. After all, that's what that word seems to mean at first glance.

   This reminds me of the term full-stack, some people consider it's just about being good at both frontend and backend, in my opinion a good full-stack is also a good networking engineer as well as good at customer acquisition.

   For best ROI:

   - integration must be automated and continuous

   - delivery must be automated and continuous

   - tech debt includes untested code and being late in dependency versions

   - the above should be treated as impediments

   The purpose of "DevOps" being to deliver faster from idea to production, it does necessarily include a toolchain of CI/CD/IaaS & monitoring tools. From this "DevOps toolchain", taylorists opened positions for developers that can maintain it around a software, they called that position "DevOps", which explains how we got there on having different meanings for the same word.

   I highly recommend "Continuous Delivery & DevOps: QuickStart" by Paul Swartout for a first quick read on the matter.

   Show morethread