Writing Good Code: Difference between revisions
From Federal Burro of Information
Jump to navigationJump to search
(New page: A Checklist if you will: * has a clear goal , clear requirements. * has a clear timeline for writing, developing. * easy to understand * has a debug mode * has an optional log * doesn't r...) |
No edit summary |
||
| Line 20: | Line 20: | ||
* boring. | * boring. | ||
* Prone to error. | * Prone to error. | ||
[[Category:Checklist]] | |||
Latest revision as of 18:30, 10 June 2013
A Checklist if you will:
- has a clear goal , clear requirements.
- has a clear timeline for writing, developing.
- easy to understand
- has a debug mode
- has an optional log
- doesn't reinvent the wheel.
- likely errors caught, reported, and where possible recovered from.
- external activities catch timeouts.
- uses existing libraries.
- is packaged ( rpm , msi , pkg )
- is under version control.
- is peer reviewed.
- is reviewd by users.
Why don't we write good code?
- time consuming (costly).
- boring.
- Prone to error.
