Exclusive updates on:

Seven Deadly Sins of Programming

by Marcie Jones on Aug 15, 2006 |

Let's face it, all developers have written code in the past that they now regret. Along the way, most also develop a mental list of the most egregious bad development practice to avoid in the future. Eric Gunnerson, C# Community Coordinator at Microsoft, has posted his list of the Seven Deadliest Sins of Programming:

Excessive Coupling
Inappropriately Clever Code
Deferred Refactoring
Premature Optimization
Overuse of Virtual (C#) or Overridable (VB.NET)
Overuse of Inheritance
Premature Generalization

MVP and author Bill Ryan has a list of 7 Deadly Sins including more conceptual items, such as "making too many assumptions."

What's on your list?

Related Editorial

Making the Shift from Relational to NoSQL

Cloud Identity Buyer’s Guide: Managing Identity in the Cloud

Betfair Chooses not to Gamble with Database Performance: An AppDyanmics Case Study

From Killer Apps to App Killers: The Devastating Effect of Architecturally Complex Defects

Faster PHP Through Java

Hello stranger!

You need to Register an InfoQ account or to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Community comments

How about ... by Cameron Purdy Posted

Failure to follow DRY principle ... by Sammy Larbi Posted

How about ... by Cameron Purdy

Making non-virtual the default for methods in an OO language? ;-)

(It's probably the biggest design mistake in the C# language. Welcome to the 1980s and C-front, folks!)

Peace,

Cameron Purdy
Tangosol Coherence: The Java Data Grid

Failure to follow DRY principle ... by Sammy Larbi

Although, I guess that could come under "deferred refactoring," considering that not refactoring would be deferring it for infinite time.