4 ms·

I ended up working on some software and I was deemed the email guy (it's a very small % of my job but it is the biggest pain). "I need an email when this happe

by duxup 2y ago

I ended up working on some software and I was deemed the email guy (it's a very small % of my job but it is the biggest pain). "I need an email when this happens.. and when this happens." The requests are endless and I'm convinced there are people who if they could would do their entire job from their inbox and get everything and anything an application can do via email. The insidious problem is that it never solves anything. "I didn't get the email!" is a constant refrain (yes they did, they always did). "Oh someone didn't do the thing so can you add this to the email too." and so on. It is such an abused tool.

Dylan16807 2y ago
> The requests are endless and I'm convinced there are people who if they could would do their entire job from their inbox and get everything and anything an application can do via email. That sounds like a reasonable goal for a whole lot of job duties. And yes some entire office jobs. (Excluding some direct human communication but a lot of jobs already have too much of that in situations that could have been an email.) > "I didn't get the email!" is a constant refrain (yes they did, they always did). Well having to manually check wouldn't improve that, would it?
Cthulhu_ 2y ago
I can see how that would work (email centric workflow), not unlike how some people now try to have a chat / Slack centric workflow.
- saalweachter 2y ago
  Yeah, everyone knows the proper thing to do is orchestrate it all through Emacs.
mrweasel 2y ago
We had a similar request for a sales team once: "If this fails we want an email".... Okay, but we never seen this fail, so you'll never get the email. As expected, they never got an email, because no failures. So instead they wanted an email every time the job ran (once every night), so they'd know that the job had failed, if they DIDN'T get the email. Only time that happened was because the email got trapped in a spamfilter I think. There must be thousands of copies of that email sitting in inboxes say: Job X ran successfully @ 04:30.

by duxup 2y ago

Dylan16807 2y ago

> The requests are endless and I'm convinced there are people who if they could would do their entire job from their inbox and get everything and anything an application can do via email. That sounds like a reasonable goal for a whole lot of job duties. And yes some entire office jobs. (Excluding some direct human communication but a lot of jobs already have too much of that in situations that could have been an email.) > "I didn't get the email!" is a constant refrain (yes they did, they always did). Well having to manually check wouldn't improve that, would it?

Cthulhu_ 2y ago

I can see how that would work (email centric workflow), not unlike how some people now try to have a chat / Slack centric workflow.

saalweachter 2y ago
Yeah, everyone knows the proper thing to do is orchestrate it all through Emacs.

mrweasel 2y ago

We had a similar request for a sales team once: "If this fails we want an email".... Okay, but we never seen this fail, so you'll never get the email. As expected, they never got an email, because no failures. So instead they wanted an email every time the job ran (once every night), so they'd know that the job had failed, if they DIDN'T get the email. Only time that happened was because the email got trapped in a spamfilter I think. There must be thousands of copies of that email sitting in inboxes say: Job X ran successfully @ 04:30.