Robert Irwin: A Conditional Art A Book by Matthew Simms yalebooks.yale.edu Only a mind opened to the quality of thingsThe most incidental detailIn a state of reverberationSort of underway by thenUntitled (Dot Painting)+41 More Seeing Is Forgetting the Name of the Thing One SeesPhenomenal: California Light, Space, Surface
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