The Complete Guide To Approaching Your Development Team When They Write Bad Code
We’ve all be in the following situation before; trying to “track” down a bug that’s been reported. Nothing crazy, just finding and fixing defects, when it happens. It’s about 1,200 lines long, it has switch statements nested three deep, and you think (but you aren’t sure) that it does the same thing two or three times in a row for no particular reason.
After seeing this, you start thinking about finally having a long overdue talk with your developers to introduce them to better methodologies and best practices when it comes to writing code. Without insulting or questioning them, how do you approach such a complex situation?
In this guide, you will learn:
- How to approach your developer’s bad code
- How to build the appropriate strategy before having the conversation
- How to collectively take responsibility for bad code
- How to set a coding standard within your team