Test-After Development Sins

January 28, 2012 – legacy code

A series of short articles exploring the impact of writing tests after the code is written on the implementation part of SDLC.

Sin No.1: Production Code First.

Sin No.2: Header Interfaces.

Sin No.3: Ignoring cross-cutting concerns.

Sin No.4: Increasing costs.

Sin No.5: Decreasing quality.

Nikos Baxevanis collects and shares fine-grained parts from methodologies and tools he uses as a programmer.