Wrap all side effects code in exception catchers

This is part of the Semicolon&Sons Code Diary - consisting of lessons learned on the job. You're in the architecture category.

Last Updated: 2024-06-15

When writing code for side-effects (email, slack message, web sockets message), make sure the method is either in a background job or wrapped in a try/catch statement. Otherwise there could be collateral damage / regressions to the main request should the addition have issues (which at any reasonable scale, it will)