Seam
A concept introduced by Michael Feathers in Working Effectively with Legacy Code. It refers to a place in a codebase where behavior can be changed or a dependency replaced without modifying the logic itself, and it is a key criterion for judging whether refactoring is safe.
Timeline (last 90 days)
The responsibility of the long refactor and multi-file change seat is to move the seam elsewhere in the codebase rather than rewrite the product; the evidence is a small, reversible diff relative to the branch, accompanying tests or script checks, and a clear rollback path.
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.
All Facts (2)
The responsibility of the long refactor and multi-file change seat is to move the seam elsewhere in the codebase rather than rewrite the product; the evidence is a small, reversible diff relative to the branch, accompanying tests or script checks, and a clear rollback path.
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%