We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Architects Live in the First Derivative • Gregor Hohpe • YOW! 2019
Architects must prioritize the first derivative of a system over stability, adapting to change and uncertainty rather than predicting it, to create resilient and efficient architectures.
- IT should optimize for the first derivative, not the stable state.
- Architects need to adapt to changing circumstances, not predict them.
- Automation doesn’t always lead to efficiency, as it can create more complexity.
- Architectures should be designed to handle uncertainty and volatility.
- The role of an architect is to facilitate change and troubleshoot problems.
- Architectures should be thought of as a “clutch” that allows for smooth gear changes.
- Speed alone is not enough, and architects must consider the entire system.
- The first derivative of a system is more important than its stable state.
- Automation and architecture can help create a faster and more reliable system.
- Disposability is a key concept in IT, as it allows for easier experimentation and iteration.
- Architects should prioritize the first derivative of a system, not just its stability.
- Friction in an architecture can slow down the system.
- An architecture should be designed to handle uncertainty and volatility.
- The option to buy or sell is valuable because it allows for flexibility in decision-making.
- The first derivative of a system is like a “hidden gear” that enables it to adapt to change.
- The role of an architect is to help organizations adapt to change and deal with uncertainty.