On the Situations and Names of the Winds is the title of a fragment of a pseudo-Aristotelian treatise, most likely written by a later author of the Peripatetic school. The two-page work identifies and briefly describes the names not just of the four anemoi, but gives a wind-name to each of the twelve points of the so-called “wind-rose”, slightly less poetically the “compass rose”, which is the figure seen on classical nautical charts and maps that shows the cardinal points as well as points intermediate.
...In both agricultural and maritime settings, the names of the winds were at once practical and phenomenologically basic: to step outside and to feel them was to know how things were in the most basic sense, to “know which way the wind is blowing”, as we still vestigially say, and to find the language to speak of it.
...If I were ever permitted to teach a course on the philosophy of wind, I would begin with the questions: How did the winds lose their names? And what does it mean for us to live in a world of nameless winds? I step outside and I feel a gust. “That’s wind,” I think to myself, and I have nothing more to add beyond that. I don’t know the winds.
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'.