Style is an often overlooked but very critical attribute of writing. The style of writing directly impacts the readability and understandability of the end product (*)

The readability and understandability of source code are important not only for the creation of quality software products but also in creating software products that can be developed on schedule and within cost.

This document holds all coding standards and best practices that are using in KMS software projects and high-recommended to use for new development projects. We believe that applying strictly coding styles, using solid coding techniques and good programming practices in software development is a key point in software quality, performance, and maintenance.

The KMS coding conventions and best practices are compiled not only from KMS developers own experiences, but also from standard guidelines provided by technology owners (Oracle, Microsoft, Google, Facebook...) and well-known organizations are accepted by large communities.

You can find the coding guidelines for a specific technology in the list as below:

• .NET with C#
• Android (from ribot.co.uk)
• Clojure (from batsov.com)
• Java
• JavaScript (from airbnb.io)
• Kotlin (from kotlinlang.org)
• Go (from golang.com)
• Groovy (from groovy-lang.org)
• Objective-C (from raywenderlich.com)
• Python (from python.org)
• Ruby (from batsov.com)
• [Scala] (http://docs.scala-lang.org/style/) (from scala-lang.org)
• Swift (from raywenderlich.com)
• Web Front-end

As supporting for software development process, KMS provide the standards for:

• Code Check-in
• ETL
• SQL Server

In case of no coding guidelines for a specific technology listed in above, consider to use a popular coding guidelines that maintainces by community at this link https://github.com/Kristories/awesome-guidelines