How we change what others think, feel, believe and do

| Menu | Quick | Books | Share | Search | Settings |

C Style: Standards and Guidelines (contents)

CHAPTER 11 : Implementing Standards


CHAPTER 11 : Implementing Standards
11.1 Raising awareness of the need for standards
11.2 'Disadvantages' of coding standards
11.3 Getting the standards defined
11.4 What should the standards contain?
11.5 Getting the standards into use
11.6 Prove the value
11.7 Keeping the standards alive
11.8 Making sure the standards are used
11.9 Summary

<--Prev page | Next page -->


11.7  Keeping the standards alive

You can not be expected to get it completely right first time, so you must make provision for how the standards are to be changed.

There should be a review several months after the first formal introduction of the standards (probably at the end of the pilot). After that, the standards may be reviewed at an agreed-upon period (typically yearly) or under special circumstances otherwise.

Beware of people using reviews to commit acts of sabotage, trying to 'bring back the good old days' or to re-implement their favorite variation. This is unlikely, but you may still find the odd 'real programmer' skulking in the cupboard.

Old standards and guidelines should not be thrown away all together, but they should be removed from public view. Put them in an archive, put the archive in the drawer, and hope that you don't have to take it out again (if you do, you'll be glad you kept them).


Site Menu

| Home | Top | Settings |

Quality: | Quality Toolbook | Tools of the Trade | Improvement Encyclopedia | Quality Articles | Being Creative | Being Persuasive |

And: | C Style (Book) | Stories | Articles | Bookstore | My Photos | About | Contact |

Settings: | Computer layout | Mobile layout | Small font | Medium font | Large font | Translate |


You can buy books here

More Kindle books:

And the big
paperback book

Look inside


Please help and share:


| Home | Top | Menu |

© Changing Works 2002-
Massive Content -- Maximum Speed