If you understand it by reading it once, it is probably a good source of inspiration. A good way to reach this objective is to read and getting inspired by other people's code. Your first goal when coding is to make your code do what you want it does. « Premature optimization is the root of all evil. » – Donald Knuth With that being said, here are the three basic rules to get yourself in the clear: Again, this is according to your judgement. If you break many of them, you may have to change something. If you have a good structure, do not change your code to enforce a single arbitrary rule. If a rule states for example that it is better that a line of code doesn't go over 80 characters, it doesn't mean that any line must not go over 80 characters sometimes, the situation needs it. In the domain of development, any rule is a rule of thumb. The fourth part ( Conversion from earlier versions) is a hopefully helpful, short guide about useful new commands or syntaxes to replace the old ways.The third part ( Equivalent commands performance) mentions commands that in appearance have identical effects but may differ in terms of performance according to the use you may have of them.The second part ( Code optimisation) is about improving performance, sometimes trading it against code readability.The first part ( Rules) will focus on having a clean, readable and maintainable code.This article will try to be a general guide about improving your code and its performance. For conception optimisation, see Mission Optimisation. 5 Equivalent data structures performance.4.22 toLower/toUpper vs toLowerANSI/toUpperANSI.

4.19 Global variables vs local variables.

4.2 loadFile, preprocessFile and preprocessFileLineNumbers.3.4 Concatenating multiple small strings together.3.1 Scheduled and unscheduled environment.

Arma 2 vs 3