No ordinary objects Abandoned by the world, no longer of use, but still carefully repaired and preserved, these were no ordinary objects. The reasons for their maintenance remain a mystery. At this point, they could only be described as "art". No—not so much "art" as something that exceeds art... Hyperart. Genpei Akasegawa & Matt Fargo, Hyperart: Thomasson artrepairthomassonsobjects
Hyperart: U.S. Rail The steepest grade on U.S. main-line track is at the small town of Saluda, on a Norfolk Southern route between Spartanburg, South Carolina, and Asheville, North Carolina. The grade goes on for three miles at a slope of 4 or 5 percent. Trains have not been running on the line since 2001, but the tracks are still maintained. Brian Hayes, Infrastructure: A Guide to the Industrial Landscape thomassonsgeographytransportation
Thomassons This was 1982, the year that Gary Thomasson was batting cleanup for the Yomiuri Giants. Thomasson had the unfortunate nickname of "The Electric Fan", which, if you think about it, was exactly what he was. Night after night, he stood in the batter's box, whiffing mightily at the ball, down on three strikes every time. He had a fully-formed body and yet served no purpose to the world. And the Giants were still paying a mint to keep him there. It was a beautiful thing. I'm not being ironic here either. Seriously, I can't think of any way to describe Gary Thomasson but as "living hyperart". Genpei Akasegawa & Matt Fargo, Hyperart: Thomasson sportsthomassons
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