Twelfth Post!

[hoisinsauce]

POST NAMER TBC-- work harder, meme!

Welcome back, anyway! Chat fandom, media, creative things, weirdness from around the net, funny stuff, anything! Meme awaits!

(start a comment thread by replying to this post)

 

Comments

Re: Coding

[(Anonymous)]

Me: When a client's data changes significantly, I would like it if we sent an email to the client's support team informing them of the change.

Tech Spec: You're absolutely right! It is vitally important for the client's support team to be informed of any changes to their data. Here's how we can accomplish this:

📨 Create a service that detects changes in client data and submits a email request.
📨 Build an API that will take in the name of a client and determine the correct recipients for the email.
📨 Design a service that uses the email recipient API and then sends emails to the appropriate recipients.
📨 Set up a state orchestration service that will move email requests between the NEW, RECIPIENTS_FOUND, EMAIL_SENT, and COMPLETED statuses.

It is also important to remain compliant with all standards. To do that, we must enable robust logging and metrics. I propose the following metrics, to be tracked on a dashboard:

📈 # of emails sent
📈 # of unique recipients
📈 % of emails that contain the letter Y

I estimate that building and testing this project will take at least 15-17 weeks.

Re: Coding

[(Anonymous)]

> 📈 % of emails that contain the letter Y

Now that's the kind of logging that every enterprise needs. Ship it!

Re: Coding

[(Anonymous)]

Add on an extra week for the meetings to decide whether that includes lowercase "y".