You will Never get time to clean your messy code
Is it a good idea to write messy code quickly and plan to clean it later?
As developers, we sometimes want to deliver functionality as quickly as possible, even by writing messy and thinking we can clean code later. One of the reasons for writing messy code might be pressure from the boss to deliver functionality ASAP. After deployment, we will be happy to see the messy code working as expected and get appreciation from the boss.
So, what is the problem with writing messy code? It is very difficult to maintain the messy code. By adding new features repeatedly with messy code, we will lose control of our code base and result in bad performance, which can cause the application to be slow. Businesses will not be happy to use the application. We will no longer be able to add new features quickly with messy code. Then pressures come from your boss and business, why you are not able to add new features.
Never write messy code to avoid this type of situation; plan to clean it later. Because, in programming, “Later equals to Never”. You hardly get time to clean the code once you deliver the functionality. If you have pressures from your manager or different stakeholders like businesses, explain why you are taking time to deliver the functionality and the advantages of writing clean code like application performance, easy to add new features in future easily,..etc.
The advantages of writing clean code are easy maintainability, application performance, ease of adding new features, fewer bugs (if any, easy to fix) and no or less frequent application crashes.
