Quotes About Development

Because our goal is to enable small teams of developers to independently develop, test, and deploy value to customers quickly and reliably, this is where we want our constraint to be. High performers, regardless of whether an engineer is in Development, QA, Ops, or Infosec, state that their goal is to help maximize developer productivity.

we are all lifelong learners who must take risks in our daily work.

developers should be able to understand and update the code of a service without knowing anything about the internals of its peer services. Services

But that's like throwing gasoline on the fire. 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.

Without automated testing, the more code we write, the more money it takes for us to test.

If you don't find problems quickly, you end up finding them months later. By then, the problem is lost in all the other changes that every other developer made, so the link between cause and effect disappears without a trace.

In other words, when we conflate deployment and release, it makes it difficult to create accountability for successful outcomes—decoupling these two activities allows us to empower Development and Operations to be responsible for the success of fast and frequent deployments, while enabling product owners to be responsible for the successful business outcomes of the release (i.e., was building and launching the feature worth our time).

a small number of reliable, automated tests are almost always preferable over a large number of manual or unreliable automated tests.

Locality in our code is what keeps systems loosely coupled, enabling us to deliver features faster.

technical debt is what you feel the next time you want to make a change.

Mike Rother says that it almost doesn't matter what you improve, as long as you're improving something. Why? Because if you are not improving, entropy guarantees that you are actually getting worse, which ensures that there is no path to zero errors, zero work-related accidents, and zero loss.

habits are what enable mastery.

practicing five minutes daily is better than practicing once a week for three hours. And if you want to create a genuine culture of improvement, you must create those habits.

practicing five minutes daily is better than practicing once a week for three hours.

When r&d capital is locked up as wip for more than a year, not returning cash back to the business, it becomes almost impossible to pay back the business,

I could wave this magic wand, I would change this step. Instead of getting source code or compiled code from Dev through source control, I want packaged code that's ready to be deployed.

Chuck Rossi, Director of Release Engineering at Facebook, described, "All the code supporting every feature we're planning to launch over the next six months has already been deployed onto our production servers. All we need to do is turn it on.

our goal is to create fast feedback and fast forward loops wherever work is performed, at all stages of the technology value stream, encompassing Product Management, Development, QA, Infosec, and Operations. This

THE PROBLEM: SOMETHING IN YOUR ORGANIZATION MUST NEED IMPROVEMENT (OR YOU WOULDN'T BE READING THIS BOOK)

Improving daily work is even more important than doing daily work.' The

The team quickly made a surprising discovery: only 50% of the source code in their development and test environments matched what was running in production.

failure results in reflection and genuine inquiry.

the leader's role is to create the conditions so their team can discover greatness in their daily work.

Work is not done when Development completes the implementation of a feature—rather, it is only done when our application is running successfully in production, delivering value to the customer.