What should you do if you see something clearly bad in an already delivered code?

If a clearly poor part is found in already completed and delivered code, it is important to act carefully and professionally:

• Assess the severity of the problem. Is it a bug, vulnerability, architectural violation, or just poor style?
• Document the problem. Record what exactly is bad and why, with examples.
• Discuss with the team. It is better to raise the issue in a team meeting or in a task tracking system, rather than making changes alone.
• Propose a solution. Instead of criticism, give specific recommendations for fixing.
• Prioritize the fix. If the problem is critical — initiate a bug fix or refactoring.

It is important not to blame the authors, but to focus on improving the quality of the product. This approach helps maintain a healthy team atmosphere and gradually improve code quality.