This article focuses on ever changing field of computer programming. There are lots of professionals who haven't written a line of production code in over a decade. Consider the academic worlds deep-seated belief in formal methods for building software, in particular formal specifications for representing requirements. The state of requirements practice has moved, over the last couple of decades in which academe has been pursuing its mathematical approaches, from a belief in the need for a fixed and rigid collection of requirements to the need for a collection of fluid ones whose change is managed. That evolution has not been reflected in the writings of those who believe in formal specifications. Little has been said about the modifiability or maintainability of formal specifications in the face of managed change, as if the academic world is not aware that the underlying needs of the field have changed.