- Forcing Functions -there are some things you can do to force issues up to the surface.
- Dig out an old or cheap phone and try to run your app on it. Any major performance bottlenecks will suddenly become obvious
- Pretend you’re a new developer in the team1. Delete the project from your development machine, clone the source code and set it up from scratch. Gaps in the Readme file and outdated setup scripts will soon become obvious
- Try to add support for a completely different database. Details of your current database that have leaked into your data layer abstractions will soon become obvious
- Port a few screens from your front-end app to a different platform. For example, write a command-line interface that reuses the business and data layers untouched. “Platform-agnostic” parts of the architecture might soon be shown up as anything-but
- Put your software into the hands of a real user without telling them how to use it. Then carefully watch how they actually use it
- DRY, or Don't Repeat Yourself
"Today the 'software' comprising the carefully planned interpretive routines, compilers, and other aspects of automative programming are at least as important to the modern electronic calculator as its 'hardware' of tubes, transistors, wires, tapes and the like" (http://www.maa.org/mathland/mathtrek_7_31_00.html
, accessed 02-02-2010).