Code Writing

While there are not specific rules for the code you will write, there are a number of coding guidelines that should be followed. Most of these can be found in the documentation.

Best practices

There are documented coding guidelines that Arts Management Systems developers should follow.

Security Practices

Arts Management Systems developers are expected to stay current on issues and potential security vulnerabilities in the technology used in the Arts Management Systems product. Arts Management Systems architects will be responsible for monitoring these areas and escalating to management when an issue arises that needs to be addressed in a future product release.

In Code Documentation

In-code documentation is required for all new code as described in the coding practices.

Protected Classes

There are a few areas of the application that are critical for the stability of the product. As such they are the responsibility of the senior developers and architects to maintain. These are called protected classes and you need to contact the architect if you need to work with them and have a mandatory code review after you change them.

Defect tracking notes

As you work you should keep track of the units you change and what the overall changes to those units are. This can most easily be added to the check in notes in the VCS.