Rules

Secret ingredients to quality software

Edit
Info

Do you know you should always refer to rules instead of explaining it?

Last updated by Brady Stroud [SSW] on 04 May 2021 02:43 am (about 1 month ago) See History

It is important to refer to your standards when trying to explain a concept. This process ensures you always give the most up to date information and that the documentation gets updated when needed. They will then know where the standard is so they can refer to it later.

When a new programmer on your team needs to get up and running on the SharePoint image you know the right and wrong way to say it.

Sit with John Liu and he will get you up on our SharePoint image

Bad Example: Explain how to run the SharePoint image

Get the URL to the standard from our intranet, if the standard is unclear, check your changes with John Liu and then make them

Good Example: Refer to SharePoint rules

Adam CoganAdam Cogan

We open source. This page is on GitHub