It's so satisfying to look at a block of code, feel a sense of unease, draw out expected behavior, draw out actual behavior, ID the bug, and fix it. SO much easier to do this when you write Tests. #cleanYourCode#messyCodeIntroducesBugs
While everyone thinks automation will make work easy, sometimes, it can go haywire. It is easy to find duplicate codes over and over again, which may lead to multiple bugs in your code. Creating a common abstract code to these methods/codes will make work easier. #CleanYourCode
A lot of times, a #code doesn’t start off being too long. But, over time as the functions grow, it will accumulate too many responsibilities. The best way to get rid of long-class issues is to separate the concerns into individual methods that have a single focus. #CleanYourCode
Having your code perform all its necessary actions can sometimes get messy. If the code has multiple responsibilities, it may result in code smell, leading to test failures. The best way to tackle this is by separating and organising each concern. #CleanYourCode