This site uses cookies. By using our site, you agree to our Privacy and Cookie Policy

Why, where and when to use Coding Conventions


The quality of code development has several aspects, so adhering to certain rules when writing code is important. This applies not only to formatting but also to many other factors, determined by the corresponding coding convention for the selected programming language and the selected development framework.

The importance of adhering to a coding convention, as well as a unified style of writing code, and following certain rules when building an architecture, is hard to overestimate.

These are important points in the development of code, and in many ways, they are the key to the success of the product in the future. 

Let's see why, where, and when to use the coding conventions.

What is Coding Conventions

The code formatting standard is generally accepted and used by a group of software developers to uniformly share code. The purpose of adoption and use of the standard is to simplify the understanding of program code by a person, and minimize the load on memory, thinking, and vision when reading a program.

An example of a coding standard is a set of conventions adopted in any common printed work in a language (for example, the C standard for coding, which received the acronym K&R, comes from the classical books of C by Kernighan and Ritchie). Another example is a widely used library or API (for example, the distribution of the Hungarian notation was clearly influenced by its use in the Windows API, and most coding standards for Python use, to one degree or another, the PEP standards).

Language developers also release detailed coding guidelines. For example, Microsoft’s C # coding standards and Oracle’s Java coding standards have been released. The coding manner proposed by the developer or accepted by well-known sources is more or less supplemented and refined in corporate standards.

Typically, a coding convention standard describes:

  • ways of choosing names and the used case of characters for variable names and other identifiers:
  • writing the type of the variable in its identifier (Hungarian notation) and a cast of characters (lower, upper, "camel", "camel" with a lowercase letter), the use of underscores to separate words;
  • indentation style for logical blocks - whether tabs are used, indent width;
  • a method for placing brackets bounding logical blocks;
  • the use of spaces in the design of logical and arithmetic expressions;
  • comment style and the use of documentary comments;
  • variable, class and file naming conventions;
  • statement style and best practices of their usage;
  • file organization;
  • declaration of classes and interfaces;
  • programming practices.

Outside of the standard, the following are implied: 

  • lack of magic numbers;
  • restriction of the size of the code horizontally (so that it fits on the screen) and vertical (so that all the code of the file is held in memory)
  • as well as a function or method to the size of one screen (for some programming languages).

Why use coding Conventions

Coding standards are important for software developers for several reasons:

  • 40% - 80% of the total cost of software is spent on its maintenance.
  • Software is almost never fully supported by its original author.
  • Coding standards improve software readability by allowing developers to understand new code faster and better.
  • Like any other product, the software must be "well packaged" and clean.

As the developers of Svitla Systems note, “The project should be written in the same style. This is necessary both to improve support and speed up involving new developers and to prevent the writing of new bicycles or the use of unnecessary patterns in the project, where it is not needed at the moment."

In our experience, the coding convention improves code readability, facilitates the introduction of new developers on the project, and simplifies code writing, because there is an understanding of in what style it should be written, and therefore less refactor later (if standards are well written with architecture and structure).

The main reasons for using the coding convention are as follows:

  1. The same rules for writing code make it easy for other colleagues to understand
  2. It is easier to understand the code in a year or 5 without the need to read each term
  3. You always know where certain classes and files are in a huge project

In general, this is the cleanness of the code, which simply speeds up the work. This can be compared to a desktop: if everything is neatly arranged, it is easy to work. If there is a mess, then every little thing takes a long time to find.

Very often Coding Conventions for each team are different, and sometimes very different from project to project. We need them so that other developers can easily figure out the code and in general, the code written by different team members looks the same within the project and is maintainable and supportable.

For various programming languages, there are coding conventions. These coding conventions are not absolute. In each project and in each company, standards can be developed for the coding convention. Here is a chart for example:

Programming LanguageCoding Convention
CGNOME C Coding Style
C++Google C++ Style Guide
C#Microsoft C# Coding Conventions
GoCode formatting and naming convention tools in Golang
JavaOracle Java Code Conventions
JavascriptGoogle Javascript Style Guide
RubyClearwater Ruby Coding Guidelin
ScalaScala Style Guide
SwiftGoogle Swift Style Guide

Where and When to use Coding Conventions

It is worth noting that coding convention is not just formatting. 

Answering the question of when to use the coding convention, the easiest option is when writing the code itself. This provides for familiarization of all project participants with the convention and coordination of all necessary requirements.

Coding Conventions

Convention coding must be applied both by a single developer and by a development team.

Regardless of the qualifications of the developers, they must use the coding convention; this makes the software development process more stable and the code turns out to be better.

Note that during the Software peer review, compliance with the coding convention is very important.

The verification process of the coding convention can also be carried out during refactoring. This improves code readability and makes the whole project more unified.

Standardization of coding conventions can be adopted at the following levels

  • Project level
  • Company-level
  • Developer Community Level
  • Industry Standard Level
  • ISO Level


Our developers from Svitla Systems work according to conventions established and agreed upon with customers.

This applies to various programming languages and various frameworks.

Svitla Systems project managers and developers usually work with the following codebase options:

  • fully fit into the customer development environment and integrate into the team, accepting the coding convention as a whole
  • if the customer has not chosen a coding convention, our developers will always advise the best coding convention for this project
  • if required, our developers can make changes to a certain coding convention and accept it for development
  • if required (in very rare cases), our developers can write the necessary coding convention for the selected project, and follow it to conduct the project

Svitla Systems follows a high code development culture. This applies to strict adherence to the coding convention, as well as building a clear project architecture, developing unit tests, and adhering to agile (scrum) methodologies. 

We always do the code correctly so that it can be supported in the future, is easy to understand and it is easy to complement the team with new developers.

The Svitla Systems company can also revise an existing project according to the coding convention; we know how to go through the process of unification and standardization of the code for the desired programming language and selected framework.

by Svitla Team
August 28, 2020

Related articles

Modern IDE for programming
by Svitla Team
June 16, 2022
Tips for building contextual help in web applications
by Olena Shevchenko, Senior UI/UX Developer
March 30, 2022
System Development Life Cycle
System Development Life Cycle
by Svitla Team
December 10, 2021

Let's meet Svitla

We look forward to sharing our expertise, consulting you about your product idea, or helping you find the right solution for an existing project.

Thank you! We will contact very shortly.

Your message is received. Svitla's sales manager of your region will contact you to discuss how we could be helpful.