Okay, so basically, I have also defined a set of coding guidelines, and which is followed by my team currently. So which includes writing clean code, and defining the variable name in a certain manner, and throughout the whole, throughout the whole application, so that it remains consistent. And then checking the complexity of the methods, suppose, in Android Studio, we can easily check the complexity of the methods using easy plugins, which is one of the plugin is a code complexity in Android. So we can using that we can easily check the complexities of every method. So it should be what do you say? It should be kept in mind that the complexities of a particular method should not exceed 10. So basically, a cyclomatic complexity refers to the number of complex refers to the complexity of the loops present inside a method. Suppose there is a particular requirement where you are receiving an intent and based on that intent, a broadcast receiver is defined in a method scope. And that broadcast that intent has many actions, suppose four to five actions. So instead of using if else loops that may increase the complex cyclomatic complexity of the methods, we can simply use a switch case to optimize our code and maintain it for the further users. So such guidelines are set within the team to write a clean and maintainable code. And also not to create many variables unnecessarily also to clean up the code and not leave anything commented and also provide commenting to each and every methods or for basically which is called as Java doc. So since I'm coding in Java for Android, so we use Java doc to provide the functionality of each and every method and what it's it is doing. Other than that, there are also many other coding guidelines we follow. So some are our own defined and some are provided by the client. So we need to follow that to the letter.
