Endurance For Alfred North Whitehead, a car accident and the exposure of a pyramid to the sun on any given day are equivalent events: We are accustomed to associate an event with a certain melodramatic quality. If a man is run over that is an event comprised within certain spatio-temporal limits. We are not accustomed to consider the endurance of the Great Pyramid throughout any definite day as an event. But the natural fact which is the Great Pyramid throughout a day, meaning thereby all nature within it, is an event of the same character as the man's accident, meaning thereby all nature with spatio-temporal limitations so as to include the man and the motor during the period when they were in contact. Alfred North Whitehead, The Circus time
The value-destroying effect of arbitrary date pressure on code An Article by Gandalf Hudlow iism.org The mandate from above is clear, just get it done! Avoid everything that's in the way: all advice, all expertise, all discovery efforts that detract from hitting the Date™! What these organizations don't realize is that all software change can be modeled as three components: Value, Filler and Chaos. Chaos destroys Value and Filler is just functionality that nobody wants. When date pressure is applied to software projects, the work needed to remove Chaos is subtly placed on the chopping block. Work like error handling, clear logging, chaos & load testing and other quality work is quietly deferred in favor of hitting the Date™. Driving engineers to an arbitrary date is a value destroying mistake agileplanningqualitydiscovery