Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Related Rants
Co own a service with another team.
Service is something me or my team have hardly worked on. Other team have far more knowledge on it. There is no active development that we do on it so no opportunity to really learn on it.
Some months back was involved in migrating the tests of this service to run on another system. I was unsuccessful and asked this other team a lot for help. This was just migrating, nothing to make you more familiar with code etc but just seeing the config and wondering what to change. The CID team then said we could temporarily add this service to use old system for builds.
Now get request from CID team they're diagnosing the issue for the service and that if they need help if we'd be able to help. I said other team better as they understand better. Manager of other team then replies with big message tagging my manager and PO and frankly says why the fuck am I forwarding this to other team, we should learn the service too as co owned. While I get their point, shouldn't stop assisting another team for the sake of knowledge transfer, should have other dedicated sessions for that.
Would be open to hear thoughts, is she in the right here? Frankly we already own loads of other stuff and never have time to look at this service that somehow the team owns
rant
question