Fast, slow, slower rhythm

1. You quickly deliver release 1.0 of a system, but with junky code.

2. You attempt to deliver release 2.0 of the system, but the junky code slows you down.

3. As you attempt to deliver future releases, you go slower and slower as the junky code multiplies, until people lose faith in the system, the programmers and even the process that got everyone into this position.

I read it from...

Refactoring to Patterns (The Addison-Wesley Signature Series)
by Joshua Kerievsky

Read more about this title...