The reflective era begins with the publication of software-engineering-an-idea-whose-time-has-come-and-gone in IEEE Software in July 2009 and represents DeMarco's public self-critical turn. DeMarco had been elected an IEEE Fellow in 1999, marking the institutional peak of his standing within the organization whose flagship journal he would use to publish his self-critique. Having spent three decades building, extending, and advocating for software engineering as a disciplined, measurable, methodology-grounded practice, DeMarco used this essay to question whether the project had actually delivered on its promises.
The recantation essay
software-engineering-an-idea-whose-time-has-come-and-gone is a short, pointed essay in which DeMarco argued that the emphasis on process, measurement, and risk reduction that defined the software engineering movement — and that he had personally championed, particularly in controlling-software-projects — had produced organizations better at controlling costs than at producing valuable software. The essay asks whether the discipline of software engineering had crowded out the creative and exploratory work that generates the most important software, and whether the cost of methodological control had exceeded its benefits.
This is a remarkable act of intellectual honesty: DeMarco published his recantation in IEEE Software, the flagship journal of the ieee-computer-society, the professional society most closely associated with the software engineering project he was critiquing. The ieee-recantation-essay event is the defining moment of this era and one of the most unusual self-critiques in the software engineering literature.
The arc from structured methods to recantation
The reflective era completes a trajectory that runs through the entire DeMarco KB. The structured-methods-era was premised on the belief that rigor and methodology could tame software development's uncertainty. controlling-software-projects extended that belief into measurement and quantitative management. peopleware began the pivot, arguing that human and organizational factors were more important than methodology. slack continued the pivot, arguing that organizational efficiency obsession destroyed the conditions for productive work.
The reflective era makes the implicit critique explicit: DeMarco, surveying the decades of software engineering effort, concluded that the methodological and measurement agenda had not produced the improvement it promised, and that the creative, human-centered dimensions of software work — which peopleware-thesis had identified as central — had been systematically undervalued by the discipline he helped create.
Significance
The reflective era does not repudiate the peopleware-thesis or the organizational-dynamics-era work on slack and risk. It repudiates the earlier structured-methods-era program — the measurement and control agenda of controlling-software-projects — while leaving intact the humanistic arguments that followed. This distinction is important for understanding DeMarco's intellectual arc: he is not abandoning his convictions, but refining them by questioning the part of his legacy that sat most comfortably within the software engineering establishment.