Do not assume that technical debt is a problem with your code
97 Things Not To Do Software CraftsmanshipEver saw SonarQube laden with thousands of maintainability and security issues?
97 Things Not to Do
Posts
Do not Release Code Without Automated Tests
97 Things Not To DoMost projects that I see facing serious problems lack tests. You should write tests for two things
Do not Get so busy that you stop learning
97 Things Not To DoLearning is the most vital part of a software developer’s life.
Do not Optimize Prematurely
97 Things Not To DoOnce 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.
Do not Show Separate Estimate for Unit Testing
97 Things Not To DoOnce I was asked in an interview (I was the interviewer!
Do not Copy and paste code to minimize the impact:
97 Things Not To DoHave 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?
Do not Fall for faux agile
97 Things Not To DoEnough ink is already spilled on this topic, nevertheless talking about it once again may not hurt.