12 programming mistakes to avoid
If you need any better proof that code is art, look no further than how the programmers view their mistakes. Just as the world is filled with wildly divergent opinions about painters, architects, writers, and poets, the realm of programmers can’t agree upon much beyond the requirement that the code doesn’t crash. Even this is a stretch. Some are fine with failing code as long as it recovers gracefully before the user notices.
The debates are usually born out of experience. When a developer says not to do X, it’s probably because some evening, weekend, or even spring vacation was ruined because someone around the office did X and it failed badly. X seemed like a good idea at the time but it was an intellectual trap and now the survivors want to warn the world about it.
