secretfanspace | Twelfth Post!

You're viewing

secretfanspace
Create a Dreamwidth Account Learn More

Reload page in style: site light

Expand Cut Tags

No cut tags

hoisinsauce posting in

secretfanspace

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)

Current Mood: impressed

Flat | Top-Level Comments Only

From: (Anonymous)

Update from slop-reviewing dan: just got handed a 19-page tech spec that was 'generated heavily with Cursor.' Very nice of them to include this disclaimer. Now instead of thinking that their tech spec makes no sense, I can just think that they're stupid.

From: (Anonymous)

We reckon someone at my partner's work is using AI to generate the messages that they post in slack. They keep replying with multi-paragraph messages that repeat keywords from previous messages in the channel and answer questions that weren't asked. We cannot figure out why they think this is an activity worth performing.

From: (Anonymous)

There's a few people at my workplace who do this as well. They copy-paste the Markdown formatting from ChatGPT, but it doesn't work in Slack so there's just random **'s littered everywhere that they can't even be bothered to fix up.

From: (Anonymous)

So weird. How is it easier to do that bullshit than to just reply to damn messages.

From: (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.