> Not Fixing All the Edge Cases This can also be a part of tackling very complex tasks. To prevent getting overwhelmed when implementing something huge, I some

> Not Fixing All the Edge Cases This can also be a part of tackling very complex tasks. To prevent getting overwhelmed when implementing something huge, I sometimes do what I call, "Implementing something stupid." Want to build an MMO? Build something that manages to send sync information to a multiple clients, but ignores auth, security, being cheat-proof, robustness, etc... Then once there's something running, start addressing those issues. So instead of not fixing all the edge cases, it's not implementing all the edge cases all at once. If the quick hack is well documented, written in a very encapsulated and removable way, who cares about removing it later. When it starts causing "lava flow" then it's time to remove it. http://antipatterns.com/lavaflow.htm http://antipatterns.com/lavaflow.htm