The Elephant Vanishes A Novel by Haruki Murakami On Seeing the 100% Perfect Girl One Beautiful April MorningThe Wind-Up Bird and Tuesday's WomenThe Last Lawn of the AfternoonBarn BurningSleep+1 More
Barn Burning A Short Story from The Elephant Vanishes by Haruki Murakami The first in agesFive barns worth burningI keep getting older
On Seeing the 100% Perfect Girl One Beautiful April Morning A Short Story from The Elephant Vanishes by Haruki Murakami 100% perfect
The Wind-Up Bird and Tuesday's Women A Short Story from The Elephant Vanishes by Haruki Murakami Who I was supposed to beQuittingA regular wind-up toy world this is
The Last Lawn of the Afternoon A Short Story from The Elephant Vanishes by Haruki Murakami She was wanting to break it off
A Slow Boat to China A Short Story from The Elephant Vanishes by Haruki Murakami Can you even call it memory?Never any place I was meant to be
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