Below are some brief notes I have written. For full style guides it is useful to see what actual companies are doing. Here is an example of code style conventions: http://google.github.io/styleguide/
- Commit your code changes to the repository often, this is best practice.
- Do not commit your .o file or your executable file to the repository, this is considered bad practice!
- On Functionality/Style
- You should have comments in your code to explain what is going on, and use good style (80 characters per line maximum for example, functions that are less than 50 lines, well named variables, well named functions etc.).
- Do not duplicate code (i.e. Use functions)
- Typically keep your functions to less than 50 lines.
- Name your functions and variables consistently. Meaning if you start them with uppercase letters, do so. If you use conventsion such as iMyVariable (the 'i' prefix indiciating an integer as the type), then do so consistently.
- Write comments liberall. Comments are more useful when they explain 'why' you are doing something. The 'what' is seen from the code.
- Indent your code for each nested block. This makes the code easier to follow.
If you accidently delete something you can navigate to cd .snapshot/ which will show files that have been periodically backed up for that current directory. This is yet anothe reason to make sure you are working within the CCIS systems which provide this backup service.