Software is never finished. It is impossible to not have bugs and anyone who denies this probably is either unaware of them or conveniently chose to ignore them. But.. code can be in a good state. An easily understandable and readable state. A state where it can be extended and scaled easily, leaving the developer who reads your code with a smile.

I don’t know any programmer who is not guilty of such mistakes including myself. It took me a long time before I could even tell my code was shit because I wasn’t adhering to certain norms or principles. To know the code is shit you should know what is good code. The trick to avoid all the sufferings that comes with a legacy codebase is to avoid writing bad code in the first place. Secondly, get the code reviewed and cleanup as regularly as possible. Whatever be your excuse for not doing it, it is of paramount importance to start writing clean code. A clean codebase not only takes less maintenance time and efforts to maintain but also saves you from pulling your hair out of frustration when you revisit the it again.

So, let’s first understand some common practices and guidelines developers use in the world of Android App development.