
Legacy Code: Test Existing Behavior Before Refactoring
Run nine boundary cases for a discount function, separate refactoring from policy changes, and see why preserving behavior does not certify its correctness.
Read articleARCHIVE · 02
Follow the trail from foundational concepts to practical engineering decisions.

Run nine boundary cases for a discount function, separate refactoring from policy changes, and see why preserving behavior does not certify its correctness.
Read article
Test six inputs, preserve missing and invalid states, and verify when a nil-coalescing fallback runs instead of treating zero as absence.
Read article
Use a storage protocol and recording double to verify order values, reject invalid input before writes, and preserve storage failures without a database.
Read article
Compare live variable capture, capture-list snapshots, and weak references, then store an escaping callback and execute it once after registration.
Read article
Compare a value, a class reference, and a struct containing a reference to see which mutations propagate and why struct does not imply a deep copy.
Read article