I have no idea how to do this, but the key lies in helping management make the connection between bad code that "works" and the actual cost it has to the company.
You'd need to be able to say something like "Because of a hard coded somethingorother buried deep in the code, we had to do spend a whole 2 days debugging the software, and another one going through the channels to release the fix, which cost us X hours of engineers time"
or "We spend x weeks building new features that would take y days if we were disciplined about good architecture"
or "Because we have no automated integration testing, each release eats up weeks of QA man hours to do what a CI pipeline could do in minutes..."
Once the management can see the $$$ floating away, the bad engineers start to float away....
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have no idea how to do this, but the key lies in helping management make the connection between bad code that "works" and the actual cost it has to the company.
You'd need to be able to say something like "Because of a hard coded somethingorother buried deep in the code, we had to do spend a whole 2 days debugging the software, and another one going through the channels to release the fix, which cost us X hours of engineers time"
or "We spend x weeks building new features that would take y days if we were disciplined about good architecture"
or "Because we have no automated integration testing, each release eats up weeks of QA man hours to do what a CI pipeline could do in minutes..."
Once the management can see the $$$ floating away, the bad engineers start to float away....