More on this book
Community
Kindle Notes & Highlights
CIO stands for “Career Is Over.”
Developers are even worse than networking people. Show me a developer who isn’t crashing production systems, and I’ll show you one who can’t fog a mirror. Or more likely, is on vacation.
“a ‘change’ is any activity that is physical, logical, or virtual to applications, databases, operating systems, networks, or hardware that could impact services being delivered.”
And maybe, just maybe, if things go well, in a few years Paige might be able to stop working.
What sort of patronizing shit is this, is this the 1950s?
business projects, internal projects, and changes.
Unplanned work.
You’ve just described ‘technical debt’ that is not being paid down. It comes from taking shortcuts, which may make sense in the short-term. But like financial debt, the compounding interest costs grow over time. If an organization doesn’t pay down its technical debt, every calorie in the organization can be spent just paying interest, in the form of unplanned work.”
work center is made up of four things: the machine, the man, the method, and the measures.
bill of resources.
‘Improving daily work is even more important than doing daily work.’ The
Continuous Delivery
are
shows that when IT fails, the business fails.
The DevOps Cookbook, Patrick DeBois, John Wills, and Mike Orzen.
Because developers are constantly getting fast feedback on their work: when they write code, automated unit, acceptance, and integration tests are constantly being run in production-like environments,
All this is made possible by DevOps, a new way that Development, Test, and IT Operations work together, along with everyone else in the IT value stream.
The First Way is about the left-to-right flow of work from Development to IT Operations to the customer.
The Second Way is about the constant flow of fast feedback from right-to-left at all stages of the value stream,
The Third Way is about creating a culture that fosters two things: continual experimentation, which requires taking risks and learning from success and failure, and understanding that repetition and practice is the prerequisite to mastery.
The Goal: A Process of Ongoing Improvement
The Five Dysfunctions of A Team: A Leadership Fable
Two Great Books on Kanbans
Personal Kanban: Mapping Work | Navigating Life
Getting Things Done: The Art of Stress-Free Productivity
Kanban: Successful Evolutionary Change for Your Technology Business
