One point I overlooked, the reason management needs to know the state of the code is so that when we start prioritizing feature work we can take those factors into account. Michael Feathers in one of his talks on this subject stated that if there is really bad area of the code that needs refactoring management can schedule anther feature. Then when the refactoring is done the delayed feature can then be worked on. That way value is delivered and things keep moving forward.
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.
One point I overlooked, the reason management needs to know the state of the code is so that when we start prioritizing feature work we can take those factors into account. Michael Feathers in one of his talks on this subject stated that if there is really bad area of the code that needs refactoring management can schedule anther feature. Then when the refactoring is done the delayed feature can then be worked on. That way value is delivered and things keep moving forward.