Address the issue constructively through these approaches: 1. Have a private, casual conversation focused on understanding their perspective and workflow. There may be gaps in knowledge or unclear requirements contributing to the errors. 2. Share useful resources like style guides, documentation, or code review checklists they can reference. Frame it as helping improve the team's overall code quality. 3. Suggest pair programming sessions to collaboratively work through complex features. This enables real-time guidance without singling them out. 4. If errors persist after support, document specific examples and discuss with your manager to determine appropriate next steps.

Start with an open, one-on-one discussion – Understand their workflow and any obstacles they might be facing. This conversation should uncover knowledge gaps or misinterpretations contributing to the issues. Share valuable references – Provide access to coding standards, reference materials, or review checklists to raise the overall quality of the team's work, strengthening the collective output. Promote joint coding sessions – Suggest collaborating on challenging tasks through pair programming, offering real-time guidance and fostering learning. Take appropriate action if improvement is slow – Document clear examples and bring the matter to your manager for further discussion. This method nurtures individual development and improvement

It's essential to approach the situation with empathy and understanding. Schedule a private chat with your colleague and frame it as a collaboration rather than criticism. You might say something like, "I've noticed a few recurring issues in the code that we can troubleshoot together. Maybe we can find a solution and improve our process?" Providing concrete examples and suggesting resources or practices they can follow will help. Focus on teamwork and encourage them to ask questions if they're unsure.

Throw questions to make them realise that what they are doing is wrong at first. Why did you decide to make that a global variable? Why did you give it that name? The best way to go about this is to just ask them why they chose that way ,to sound interested in their reasoning, because that is what you need to attack not their ability. But if it's regular then code reviews of each checkin is good. That way, you can review that checkin and point out the mistake in the review. You really need to try and get a manager on board to have some interest in quality of code. As you having to fix your colleagues' code is taking you away from doing your tasks.

1. Understanding the Gaps I would hold one-on-one sessions to understand any knowledge gaps. 2. Highlighting the Impact It's essential to communicate the impact of their mistakes on the project without undermining their skills. 3. Collaborative Code Review Collaborative code reviews, whether through calls or side-by-side sessions, would allow for immediate feedback and demonstrate that I value their contributions. 4. Celebrating Achievements Celebrating their successes publicly fosters motivation and reinforces that their work matters. 5. Creating a Supportive Environment Having supportive environment where team members feel comfortable acknowledging mistakes encourages growth and accountability, ultimately benefiting the entire team.