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?
Co-founder and Software Craftsperson at Incubyte
A tech evangelist and mentor, Sapan has been fuelled by two things in his 15+ year professional career; coffee and his love of designing self-motivated, high-performing and passionate software engineering teams. Being a software craftsperson at heart, he has created and coached teams of over 500 software developers spread across the US and India with the sole objective of forging exceptional software products with an unfettered focus on quality.
Ever saw SonarQube laden with thousands of maintainability and security issues?
On multiple occasions, I have worked on projects where I learned how critical testing is and that not all tests are the same.
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.
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!
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.