Writing concurrent code is hard, but testing it, is something else. I'm almost sure my implementation is flawed, but I can't get the tests to fail!

Sprint planning, we spot a risk for one of the stories: An old client wants a new feature that relies on a third-party component that has not been included in our integration tests for the last 2 years.

The risk: It's probably not compatible with the new version of our system, if that's true, we'll need to make changes to our system before starting to work on the new feature, and setup integration testing.

Management: - Are you sure it's not compatible anymore?
Me: - No, we would need to bring both systems up and test if they work, there's no automation for that right now.
Mangement: - If you have not checked it's not a risk.
Me: (o_O) ? Whatever, I've warned you.

2 Days later: Our system does not work with this third-party system anymore, we can't finish the feature this sprint.

Management: (☉_☉)

Cheers to that coworker who instead of of opening a PR with a fix writes a blogpost on slack explaining the workaround...

Guess who just opened a PR and got praised by everyone for fixing the issue?

Yes, send me a screenshot of the logs. Beacause I love having to re-type the error you just got. If only there was a way to copy paste text in Slack!

I did not know I was working with my grandma...