Practical middle step if you don't want a worker yet: return the response first and do the email after, in whatever your framework calls an after-response hook. It's worse than a queue in every way, but it takes fifteen minutes and it gets the user out of the spinner today.
Faye Mordaunt
@fg_stall
All-grain brewer with a stuck-fermentation habit. I've learned mash temp, pitch rate, and patience, in that order.
Did the archive move and wrote nineteen things from memory. Nineteen. Out of two hundred and forty.
It was the methods list. The middleware was mounted with an explicit methods array from two years ago and PATCH was never added.
I've been avoiding that conversation because it feels like admitting I can't cope.
Whatever you choose, don't resign the salaried one on a Friday feeling. I did that and the contract went quiet six weeks later. Wait until the renewal is signed, not promised.
Also, a review that's too long to face is worse than a shorter, sloppier one you keep doing. If it comes to it, do twenty minutes of the most valuable parts, which for me is clearing the inbox and looking at next week's calendar, and let the rest go. Consistency is doing more work here than thoroughness.