A sustainable software architecture is an ideal that many hope for or plan for but often fall short of. Architectural stagnation and drift is often blamed on many things, often reflecting a subtly held belief that if only it weren't for change or for deadlines all would be well.

Change and deadlines, however, are the lifeblood and drivers of any development project. The idea of a static or controlled architecture may be the problem. So what can be done to keep the architecture alive using the mixed uncertainties and certainties of development? Refactoring, recovery, re-envisioning, retrospection, re-engineering, repair and many other activities beginning with re- will be explored in this talk.