Jump to content
Sign in to follow this  
  • entries
  • comments
  • views

a working definition of good code

Sign in to follow this  
Norman Barrows


a working definition of good code

A definition of "good" code (in no particular order):

1. correct - the code should work correctly.

2. brief - brevity is preferable. but not at the sake of readability.

3. simple - simpler code is preferable to more complex code.

4. bullet proof - the code should be able to handle any input params without crashing, or BY DESIGN never get passed params it can't handle.

5. easy to work with / mod / expand / maintain. "low friction" as Johnathan Blow calls it.

6. portable - more platform agnostic code is better. code which works with different compilers, OSs and hardware can be more useful when code portability is an issue. with an eye towards future portability, code should be designed with platform agnostic syntax when practical.

7. high readability - the code should be easy to read and understand. brief and simple code can help with this.
Sign in to follow this  


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!