Michael Feathers
A software engineer and technical author known for Working Effectively with Legacy Code. He proposed core refactoring concepts such as the seam.
Timeline (last 90 days)
Characterization tests compare byte-level output, so any change unrelated to business logic (timestamps, random IDs, container iteration order) is misjudged as a regression.
Michael Feathers proposed in "Working Effectively with Legacy Code" that code without test coverage and that no one fully understands is legacy code, regardless of when it was written.
Michael Feathers proposed the concept of a seam: without modifying the code itself, one introduces test points (such as wrapper functions, dependency injection points, link-time substitution) to isolate the logic to be changed, thereby obtaining a verifiable boundary for changes in a legacy system that lacks complete tests.
A seam is a concept proposed by Michael Feathers in "Working Effectively with Legacy Code", referring to a place in a codebase where behavior can be changed or a dependency replaced without modifying a piece of logic itself.
The concept of "seam" was first systematically proposed by Michael Feathers in his book Working Effectively with Legacy Code (2004).
Feathers defines a seam as a place in a program where you can alter behavior without editing the code at that place.
All Facts (6)
Characterization tests compare byte-level output, so any change unrelated to business logic (timestamps, random IDs, container iteration order) is misjudged as a regression.
50%UnverifiedMichael Feathers proposed in "Working Effectively with Legacy Code" that code without test coverage and that no one fully understands is legacy code, regardless of when it was written.
50%UnverifiedMichael Feathers proposed the concept of a seam: without modifying the code itself, one introduces test points (such as wrapper functions, dependency injection points, link-time substitution) to isolate the logic to be changed, thereby obtaining a verifiable boundary for changes in a legacy system that lacks complete tests.
50%UnverifiedA seam is a concept proposed by Michael Feathers in "Working Effectively with Legacy Code", referring to a place in a codebase where behavior can be changed or a dependency replaced without modifying a piece of logic itself.
50%UnverifiedThe concept of "seam" was first systematically proposed by Michael Feathers in his book Working Effectively with Legacy Code (2004).
50%UnverifiedFeathers defines a seam as a place in a program where you can alter behavior without editing the code at that place.
50%