Sherman does not appear to understand what waterfall is or why people rewrite code. Waterfall specifies that phases of a single implementation are performed on

Sherman does not appear to understand what waterfall is or why people rewrite code. Waterfall specifies that phases of a single implementation are performed one after the other, completing one before the next phase begins. The classic example lists this as "design->coding->testing". What Sherman is describing is "iterative design," where you build something, put it in front of customers, then make changes suggested by customers (or maybe there was a list of features you wanted to add yourself.) Throwing away code is okay if it leads to "better" code where better means faster, easier to fix, smaller code size, etc. Often you do not know what the issues with your code are until you write it. Writing code for "experimental" purposes is decidedly iterative, not waterfall.