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).

Did you try throwing it in the oven at it’s highest possible temperature? Gotta reflow that solder and the board will magically come back together in one piece!

Which is probably a net positive on their lives. The less social media the better.

Yeah that’s cause they’re using ancient systems that probably store the password in plaintext. If you absolutely must use it make sure that password is only used on that specific site. I would strongly recommend looking for other ways before you do though.

If it’s a package I’m not familiar with and is relatively small/unknown then I’ll give it a brief once over to see if there’s anything that sticks out (obfuscated code, making http requests when the package should never do that, etc.). Most of the time though it is just trusting the FOSS community.

Of course they re-invented the bus. It’s like carcinisation but the end product is always trains or busses., but if this means less cars on the roads I think I’m for it. As long as cities don’t get lazy and use this an excuse to cut their bus programs.