One of our Human Factors Engineers just asked us to compile a list of “what makes good code”. He had a few initial suggestions, and they were added to for the following list. Although I think we are aware of certain principles, how do we create a checklist of what is “good” versus “poor”.
- The code is valid
- Inline comments are used consistently and effectively
- Alignment and structure of the code display allows for easy scanning and reading
- The code is accessible
- Tables are not used for layout
- CSS is used appropriately via an imported style sheet, a linked style sheet, or styles in the header (in that order).
- The code is as slim and compact as possible
- The code uses semantic markup
- Inline styling and scripting is kept to a minimum
- Graceful degradation is kept in mind
Related posts:
- Subscribe to the RSS feed
- Get Email updates
- Tweet This
- Stumble It
- Add to del.icio.us
- Share on Facebook
- Email to a friend
