C NativeScript conventions
Conventions exist everywhere in the real world, and make our lives easier by reducing the number of decisions you need to make daily. Take learning to drive a car as an example – conventions (or rules of the road) are everywhere: drive in the right-hand lane, red lights mean stop, a car with a left blinking tail light means it’s going to turn left, and flashing lights or signs generally mean caution – watch out! Without these conventions, you could drive, but it may not be nearly as safe or productive as you’d like.
Just like the rules of the road make driving easier, software development conventions make being a developer easier. But, understanding conventions is important for reasons other than making development easier. Conventions establish a standard or baseline for how code should be written and organized. When writing software, you should expect others will need to update, add to, or maintain the code you have written. By following agreed-upon standards and conventions, your code is more maintainable (which should be one of your goals as a developer). Often, developers feel their job is to be the fastest developer (with a goal of writing the fewest lines of code), but that’s wrong. Instead, you should be focusing on writing descriptive, easy-to-read code. In doing so, you allow other developers to better understand the purpose of your code, thus making it more maintainable.