Wouldn’t retrospectives be the best time to bring this up?
As a senior developer, why are you turning to Reddit for advice? Shouldn’t you be able to handle this yourself?
It’s not your job to micromanage your colleague. Focus on collaboration and leading juniors instead.
Start by having a casual conversation with the backend dev. If there’s no improvement, then mention it to your manager.
If you have a ticketing system, file bug reports instead of messaging him. This ensures accountability.
Be cautious about throwing coworkers under the bus. Focus on your work—there’s a broader organizational issue at play.
Have you tried talking to him like an adult?
A front-end dev calling their colleague lazy—wonder why the backend guy is burned out. If you’re waiting on him, you might end up picking up extra responsibilities when he leaves.
You’re a senior professional, so you should have a direct conversation with your colleague. Ask how you can help him. It’s your responsibility to keep the team functioning.
Dallas said:
You’re a senior professional, so you should have a direct conversation with your colleague. Ask how you can help him. It’s your responsibility to keep the team functioning.
Not caring about work is a bad approach, especially as a senior.
Why would you bother? You won’t be rewarded for your loyalty.
It really sounds like you’re meddling in things that aren’t your concern. If you’re unhappy, consider looking for a new job.
Consider a conversation framed around improving processes and collaboration rather than accusing him of not trying.
Focus on what you can control. Document issues and use your ticketing system to handle bugs effectively.
Make a Playwright test suite for the endpoints based on the requirements you both agreed upon. It benefits you both.
I’ve learned that sometimes being the best means slowing down to maintain good relationships with teammates.
Collaborate more closely, perhaps by pair programming or reviewing each other’s code. That might help address the issues directly.
You need a formal bug-tracking system and proper QA to manage performance concerns without it coming off as personal.
Make sure to have retrospectives to discuss these kinds of issues as a team.
Consider formally testing his work upon delivery. You can then work on alternatives while waiting for fixes.