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
The heart of systems engineering While the client has some knowledge of his symptoms, he may not understand the real causes of them, and it is foolish to try to cure the symptoms only. Thus while the systems engineers must listen to the client, they should also try to extract from the client a deeper understanding of the phenomena. Therefore, part of the job of a systems engineer is to define, in a deeper sense, what the problem is and to pass from the symptoms to the causes. Just as there is no definite system within which the solution is to be found, and the boundaries of the problem are elastic and tend to expand with each round of solution, so too there is often no final solution, yet each cycle of input and solution is worth the effort. A solution which does not prepare for the next round with some increased insight is hardly a solution at all. I suppose the heart of systems engineering is the acceptance that there is neither a definite fixed problem nor a final solution, rather evolution is the natural state of affairs. This is, of course, not what you learn in school, where you are given definite problems which have definite solutions. Richard Hamming, The Art of Doing Science and Engineering: Learning to Learn What the problem isComplete and consistent requirements