How to Handle Chaos from a New Code Consultant?

I'd suggest offering a compromise with the consultant. There are some static analysis tools that allow you to implement checks gradually, focusing on new code first. This way, they might see the value without feeling overwhelmed. Just make sure that whatever you suggest goes in writing so they can't shift blame onto you if things go wrong.

If he's pushing back on using tools that are free and beneficial, it raises a red flag about his credibility. You might want to call him out on it and emphasize that a lack of static analysis can lead to bigger issues later. If all else fails, there’s always the option of showing exactly what happens when problems arise from poor coding practices.

You should start by gathering data on what happens when things go wrong after deploying without thorough testing. Have examples ready of when past updates failed due to a lack of proper testing. This evidence can help make a compelling case for why a static analysis tool is necessary.

It's pretty rare these days to find a development team that doesn't use static code analysis. If your consultant is against it, challenge him by asking for examples of successful projects that don't use such tools. Have your arguments ready! It’s not just about current tech; static analysis can save money in the long run by preventing costly bugs.

Honestly, if it gets too bad, consider looking for other job opportunities. Sometimes it's better to get out of a toxic environment than to keep fighting a losing battle. But while you're there, keep records of your discussions and decisions. If things go south, you'll have documentation to point back to.