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
Feature parity An Article martinfowler.com Whilst Feature Parity often sounds like a reasonable proposition, we have learnt the hard way that people greatly underestimate the effort required, and thus misjudge the choice between this and the other alternatives. For example even just defining the 'as is' scope can be a huge effort, especially for legacy systems that have become core to the business. Most legacy systems have 'bloated' over time, with many features unused by users (50% according to a 2014 Standish Group report) as new features have been added without the old ones being removed. Workarounds for past bugs and limitations have become 'must have' requirements for current business processes, with the way users work defined as much by the limitations of legacy as anything else. Rebuilding these features is not only waste it also represents a missed opportunity to build what is actually needed today. These systems were often defined 10 or 20 years ago within the constraints of previous generations of technology, it very rarely makes sense to replicate them 'as is'. softwarefeaturesrepair