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
Can you put an ingest test on your systems?
Throw a flag when the JSON breaks etc and track those metrics.
If they are breaking production services, they sure wouldn't last long on any of the teams I work with.
This 100% is a management issue, both their boss, and yours.
If resources are going from one team to another, and they have separate management, that damn well better be coordinated through your boss. At the very least C.C. at the start and end of the project.
I'm all for helping out another team, that's what you do, but sounds more like constantly cleaning up their messes.
It happened inside their project, not in communication with our part of the whole. It happened communicating with the code we wrote for them, but we didn't explain our code to them, so it might be a little bit of our fault, even if it was in the documentation and the tasks that were provided to us, the json was part of the documentation.
The resource I was talking about was you, not the JSON. Pulling your time away to fix it. That has to be coordinate a level above unless both teams have the same management.
If not you may your work impacted by it, as they say, cover your ass.
Oh, now I understand what you said and agree with it.
Also sounds like your software architecture may be too tightly coupled. If you are creating code that consumes input from the other team, the other team should only need to know what the expected inputs and outputs are. If they're going in and making changes to your code then you guys need to merge teams or implement a review process (like pull requests in GitHub).