this post was submitted on 28 Jul 2025
26 points (90.6% liked)
Programming
21924 readers
638 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's a job for THE MIDDLE MANAGER!! (imagine a crappy super hero)
No, seriously, do not step over your boss to talk to theirs. That's like, the job your boss has, and they might get pissed at you, and, depending on pettiness level, make your life worse. Talk to your boss, explain how and why that's a problem. Make it clear you expect them to solve it.
If and only if they say they can't do anything, you may consider talking to your boss' boss. But not the other team's boss. Before doing that, I'd have hard financial evidence, like the other commenter suggested. Log your hours in their time buckets for at least a month, get others to join you in doing the same, get a report with total amount spent. Then you turn again to your boss and maybe include boss².
Talking to the boss seems a bad idea, yeah.
I'm thinking about doing a teaching session with the whole team (for the whole project), to explain things in the grand scheme of things of how they work, this might help with what each part of the code does. The project is huge, but the teams are medium sized and we are hiring a lot of people, so it might be good for all to know a little bit more.
If they're not competent this will be a waste of time. I'm not saying it's a bad idea, just have low expectations.
That team needs technical leadership on their end who can enforce standards and quality.
That's leadership. Sounds like a plan.