1999
Martin Fowler publishes Refactoring
Martin Fowler published RefactoringRestructuring code without changing behavior — improving design while keeping tests green. in 1999 — cataloging code improvement patterns that complement his contemporaneous quote defining refactoringRestructuring code without changing behavior — improving design while keeping tests green. as behavior-preserving structure change.
What it was for
Fowler's catalog gave names to extract-method, move-field, and dozens of safe transformations IDEs now automate. He shaped agileAn iterative software development style — short cycles, continuous feedback, and adaptive planning., microservicesAn architecture splitting applications into small independent services — each deployed and scaled separately., and enterprise patterns discourse for JavaA portable language running on the JVM — dominant in enterprise servers, Android, and big data. and beyond.
People
- Martin Fowler — author
Why it's here
RefactoringRestructuring code without changing behavior — improving design while keeping tests green. vocabulary became standard in IDEs and code review culture.
Why it mattered
It legitimized changing structure without changing behavior as professional practice.
What it solved
TeamsMicrosoft Teams — chat, video calls, and Office integration for workplace collaboration. feared improving messy code without a shared pattern language.
Media
ImageMartin Fowler (software engineer)Webysther Nunes, CC BY-SA 4.0, via Wikimedia Commons