48 | | * '''Writing analysis''': After reading PROCESS, you should know what analysis is. Manual for writing good analyses -> [wiki:PLATFORM_STANDARDS_ANALYSIS_R0#Howtowriteanalysis] |
49 | | * '''Writing reports''': In the end of every working day you should submit a daily report, as well as Iteration report in the end of the iteration. How to do this: [wiki:REPORTS]. |
50 | | * '''Coding''' |
51 | | * Code Tasks Requirements: [wiki:CODE_TASKS_REQUIREMENTS]. |
52 | | * Naming Conventions: [wiki:NAMING_CONVENTIONS]. |
53 | | * Code Smells: [wiki:CODE_SMELLS]. Bad code examples. |
54 | | * Writing Javadoc: [wiki:JAVADOC_CONVENTIONS]. |
55 | | * Logging: [wiki:LOGGING]. |
| 48 | * '''Writing analysis''': After reading the Process page, you should know what analysis is. See [wiki:PLATFORM_STANDARDS_ANALYSIS How to write analyses] page for instructions on how to write a good analysis. |
| 49 | * '''Writing reports''': In the end of every working day you should submit a daily report, as well as an iteration report in the end of the iteration. See the [wiki:REPORTS Reports] page for instructions on writing reports. |
| 50 | * '''Coding''' - You should review the followin pages: |
| 51 | * [wiki:CODE_TASKS_REQUIREMENTS Code Tasks Requirements]. |
| 52 | * [wiki:NAMING_CONVENTIONS Naming Conventions]. |
| 53 | * [wiki:CODE_SMELLS Code Smells] |
| 54 | * [wiki:JAVADOC_CONVENTIONS Writing Javadoc]. |
| 55 | * [wiki:LOGGING Logging]. |