It becomes clear to me whilst working on our latest projects that when working in teams there is a clear need for better documentation of how we think and convey our solutions to other developers. In working with frame works one is limited to how one can solve a solution but when it comes to a system like TINA4 each developer can program in his own way. Now that does not mean that we all should be like zombies and be put in a box but clearly there are some good principals to follow. Here are some of my thoughts on the basics.
- Plan what you are going to do before starting, 30 minutes planning saves hours
- Prototype complex code in a sandbox
- Comment your code before you code
- Never repeat code – make objects or functions to do repetitive things
- Always code simple, simple is better
- The best code you write is the code you never have to write (thanks Boian)
Have fun coding, if you have any extra good principles to share then post them in the comments section below.