InfoQ

InfoQ

InfoQ

En | 中文 | 日本語 | Br

562,907 Jan unique visitors

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Seven Deadly Sins of Programming

Posted by Marcie Jones on Aug 15, 2006

Sections
Development
Topics
.NET ,
.NET Framework
Tags
Coding Standards
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?

RelatedVendorContent

Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat

Getting Started with Stratos - an Open Source Cloud Platform

A Guide to Branching and Merging Patterns

Kanban for Agile Teams

Case Study: IBM's Agile Transformation

2 comments

Watch Thread Reply

How about ... by Cameron Purdy Posted
Failure to follow DRY principle ... by Sammy Larbi Posted
Sort by date descending

  1. Back to top

    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

    Reply

  2. Back to top

    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.

    Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.