The Path to DevOps

Editor's Notes

• #3 1.A reaction to the same failures, over and over again. It is too dynamic, so no one process will work. 2.Cargo Cult – What an Agile Cargo Cult is, and how the Corporation is also a cargo cult 3.A silver bullet, a tool of control, and what to blame when it all goes wrong. 4.How we killed Agile by throwing the manifesto out the window, enabling certificate mills, and selling it as a product 5.Just let the team run like they want, and don’t call it Agile (a loaded term)
• #4 1.Unit Testing – Isolated versus Social 2.Service Testing – Integration versus Contract 3.UI Testing – How you can do it without being E2E. Acceptance testing limitations 4.How E2E testing is not possible in modern distributed systems – The SMS problem 5.Exploratory Testing – Using humans for what they are good at
• #5 1.Remember the Testing Pyramid – This is where you start realizing that things like Agile and Test automation are prerequisites 2.CI is three things – You can’t do thing without test automation 3.CD requires CI – Otherwise you are just breaking stuff faster 4.Continuous Deployment is possible – You just need good people and automation. Places go 100+ times a day, easy.
• #6 1.Source control is fundamental to software as config as code and code is code 2.SCM has changed greatly, and Git dominates the market at 73% as of 2022 3.Along of companies did a lift and shift onto Git, not taking into account major conceptual improvements 4.Cloning, Commits, Pushes, Branching, Tagging, Pull Requests 5.Branching strategy tends to be the number 1 thing impeding CI, and it is always unnecessary
• #7 1.The walls we built to make software 2.The attempt to quantify everything into a single process with roles 3.Decisions with no context, the blame game, turn the ship around 4.The cargo cult of corporations 5.DevOps as more of a culture than a process