A right-half-plane zero is when the exponential growth rate of an input does not affect the output. For example, eating ice cream increases happiness but creates more unhappiness so you eat more ice cream to make up for it and so on until there is no ice cream anywhere.
A system with a right-half-plane zero needs to be carefully designed because, when subjected to an input, it will have the inverse response at first. For example, when a plane attempts to climb by pitching up, it moves down first. If the pilot over-corrects by pitching up further, the input will cause the opposite effect—causing a stall and eventually crashing the plane.
Read You need to know what right-half-plane zeros are.
See also:
- The Ringelmann effect shows groups become less productive as they grow
- A Mobius strip and Klein bottle are like physical/virtual representations of right-half-plane-zeros
Links to this note
-
How to Live an Asymmetric Life (Literature Notes)
In How to Live an Asymmetric Life, Graham Weaver talks about how to confront fear and get the most out of your life to a class of soon-to-be business school graduates.
-
The Default Strategy for Dependencies Should Be to Not Add More
Adding new dependencies to a codebase is a net positive until it’s not. The added leverage of picking up an off-the-shelf solution eventually gives way to dependency hell—fixing breaking changes, incompatibilities, security issues, and so on.
-
Broken Escalators Are Still Stairs
Like the Mitch Hedburg joke, “when escalators break they become stairs—sorry for the convenience” reminds us about the importance of designing systems that fail gracefully. Escalators can still be used even when their function no longer works unlike elevators where you get stuck until it’s fixed.