97 Things !to do

Do not assume that technical debt is a problem with your code

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. We are looking into how people work! We are looking into the team's behaviour

97 Things !to do

!Release code without automated tests

Most projects that I see facing serious problems lack tests. You should write tests for two things Validating behavior of the system as you develop new features.Automating reproduction of bugs. Yes, it stands true for bug fixes too! Create a failing test case

97 Things !to do

!Show separate estimate for unit testing

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

97 Things !to do

!Get so busy that you stop learning

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. Sandro wrote in his

97 Things !to do

!Optimize Prematurely

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

97 Things !to do

!Fall for faux agile:

Enough ink is already spilled on this topic, nevertheless talking about it once again may not hurt. A team that is adopting agile must adopt its underlying spirit. Chaos is

97 Things !to do

!Copy and paste code to minimize the impact:

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? What