Ever saw SonarQube laden with thousands of maintainability and security issues? Looking at those dashboards, we often believe we’re looking at the code’s state, but there is more to it.
Most projects that I see facing serious problems lack tests. You should write tests for two things
Learning is the most vital part of a software developer’s life. Being so busy that one stops learning is neither desirable nor helpful to one’s career.
Once again, you would think that the software development community has moved past this point, but I still get many teammates who want to “save memory” using HashMaps instead of POJOs.
Once I was asked in an interview (I was the interviewer!) What do you do in situations where the customers don’t want you to write test cases, or they want you to deprioritize the activity of writing test cases.
Have you ever seen code in your module, which was so complex that you decided to copy and paste it entirely rather than changing it to accommodate your requirement?
Enough ink is already spilled on this topic, nevertheless talking about it once again may not hurt.