Put down the abstract factory and get something done

The general idea is worthwhile, but not to the extreme the author suggests:<p><pre><code> &#62; Maintainability isn't a factor. Best practices don't &#62; matter. Design patterns don't matter. All that matters &#62; is getting things done. </code></pre> Naturally, you must find a happy medium. Go for maintainability and best practices wherever possible, but don't lose sight of your goal: create your product.<p>That said, the author did acknowledge the need for moderation toward the end. Best practices are thusly named for a reason.

This is a terrible attitude. If you don't write maintainable code then the price you pay for it later is that your project eventually ends up permanently stuck in the mud.<p>There is a line that you can cross where no amount of refactoring will rescue you from the mountain of technical debt you've accumulated. Once you're on the other side of that line, your project is 'bankrupt' and other than putting out fires you're never going to get anything done ever again.