How Do You Define “Good Code”?

Previous | Next

By mswatcher
via developerzen.com
Published: Jul 05 2009 / 14:16

I was on a phone interview the other day where I was asked for my definition of “Good Code”. The first thought that came to mind was maintainability – if it can’t be understood, maintained and extended by other developers than its definitely not good.

Vote up

Vote down

Tweet Save Send Tags: opinion, reviews

Upcoming Links

See all the newest links

Comments

Add your comment

yakkoh replied ago:

-1 votes

All this is okay, but THE definition for good code is: NO BUG. None, nil, zero, nada, zilch.
All the rest is derived and defined from from this principle: no bug.

Strangely enough, these definitions are coming from a company that has notorious and numerous bugs.

antych replied ago:

2 votes

There's no code without bugs, your logic is flawed. Code needs to be simple, readable and easy to modify. Bugs are largely irrelevant as long as they don't make it to the final product.