This would be very unwise from security standpoint. Internal access to customer stuff is granular and made hard for internal staff to gain, to minimize chances of screw up intentional or not.

I have better things to do in my life than "internalizing" anything that doesn't matter in the grand scheme of things.

Or just do a merge and move on with your life.

Why is this bad? From one of the threads - "There IS scrutiny on vaccines, by the scientific and medical community - your "scrutiny" (as presumably neither a PhD in a relevant field or MD) is not valuable or relevant. There is decades of research that says that currently recommended vaccines are safe and effective."

OK, then there won't be grounds for lawsuits or lawsuits will be easily dismissed.

"you can be sure there'll be a bunch of crackpot right-wingers trying to prove each one is "bad" and they'll disappear sooner or later" - This logic can be applied to literally any product, be it a medicine, a vaccine, or any consumer good. Somehow pharma companies are able to sell any other drug without going into bankruptcy.

In NET, one would simply mock one or two methods required by the implementation under the test. If I'm using Moq, then one would set it up in strict mode, to avoid surprises if unit under test starts calling something it didn't before.

I have thousands deadlines which are suddenly coming due and a bunch of code which is broken because some poor soul under the same pressure put something that "works" in. And it worked, until it didn't, and now it's my turn in the barrel.

Is this the joy?

I'm not complaining, I'm doing it for the good money.

Odd critique. Microsoft could do whatever, it was Crowdstrike who "raw dogged" the update to customers without any meaningful staging.