Why is it important to write clean code?

Early in my career, I used to think that writing code fastly was the most important thing while writing code. When my manager gave me a task, I tried to develop fastly. As the project grew, I realized that the code became more difficult to maintain and understand. Afterward, I researched object-oriented principles, solid principles, design patterns and reviewed clean code articles. As a result of my investigations, I realized that I was doing some things very wrong and that could write much better quality code with tested methods. I realized also that slow, clean code is more important than fast, bad code.

Later in my career, I examined a lot of bad codes. Generally, a project was written by developers in the fastest way, later these codes became very difficult to maintain. Then developers started to spend a lot of time maintaining the code. Then the company decided to rewrite the project because of the software maintenance cost. If clean coding principles are not taken care of, new projects become unmanageable after years.

For these reasons, every programmer should pay attention to clean coding. Companies should also standardize clean coding principles for the software developers they employ. In this blog, object-oriented principles, design patterns, and architectural subjects experienced and learned, which are needed for clean and sustainable coding, will be included.