Why sending notifications is a nightmare for engineers

Why sending notifications is a nightmare for engineers

Sending one email is a single line of code, but doing it properly takes three months of escalating fixes. This piece traces how a simple receipt email grows into retries, idempotency IDs, backup providers, quiet hours, rate limiters, and consent checks—each step triggered by a real support ticket. Seven companies, including Salesloft, Zoho, Asana, Buttondown, Starbucks, HBO Max, and Everbridge, hit these same walls, and the author argues careful teams still get bitten.

A timeout only means you didn't get an answer. It doesn't mean the provider didn't send the email.
  1. neuroticnews25

    "04 Your users are asleep, so you add quiet hours"

    Is this a real thing? Do people really expect to not get emails while sleeping? Doesn't that go against the very concept of an async communication?

  2. InsidiousWombat

    I dunno, personally I find getting them to be a nightmare. I still winge when I hear the vibration sound from the first few years of the job when I was on call

  3. edoceo

    The email send problem seems made up, your MTA handles that. The rest feels sales-y.

  4. trollbridge

    It isn’t a nightmare. Use iOS and Android’s notification system and let the user have fine grained control to tweak how they get notifications. Include options for critical alerts.

    A very good alternate channel is Telegram for distributing to a group; Slack and Discord work too.

  5. ferngodfather

    Email alone is fine for like 90% of use cases, imo. This is neat, but to me just so obviously looks like an AI slop solution searching for a problem.

More from this day

2026-11-17