One of the really nasty things about robustness is that the things we often do to make our systems more robust in turn increase the complexity of our system, which in turn increases the surface area of new types of failure.
★ In the digest▶ 1:26:37
Sam Newman argues resilient systems come from a few simple rules, honest trade-off conversations with the business, human collaboration and clear definitions of good, with AI used cautiously within modular boundaries.
Watch on YouTube ↗Word for word
One of the really nasty things about robustness is that the things we often do to make our systems more robust in turn increase the complexity of our system, which in turn increases the surface area of new types of failure.
Programming is not typing and fundamentally it made it click for me was having those conversations with clients if the client thinks that programming is typing and That's why they don't want you to pair program. Well, then you've got a fundamental problem that needs to be dealt with. And it's not a conversation about pairing. The conversation is what do you think programming actually is?
For those last two things, sustained adaptability and graceful extensibility, this all comes down to people and culture. Like having proper environment psychological safety is just absolutely required. If you can't raise issues, if you can't challenge in a safe way, you do you will deal with surprise badly because things won't get raised and you won't learn because things will be hidden.
Free — sign in with your email, no password.