Twelfth Post!
May. 31st, 2025 06:24 pmPOST 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)
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)
Re: Coding
Date: 2025-07-25 03:17 am (UTC)class FruitConstants: """ Constants for fruit ingestion. """ APPLE_OUTPUT = 'apple_output' BANANA_OUTPUT = 'banana_output' CHERRY_OUTPUT = 'cherry_output' DURIAN_OUTPUT = 'durian_output' class FruitIngester: """ Gets output locations. """ def getOutputLocations(basePath): outputs = {} outputs['apple_output'] = basePath + FruitConstants.APPLE_OUTPUT outputs['banana_output'] = basePath + FruitConstants.BANANA_OUTPUT outputs['cherry_output'] = basePath + FruitConstants.CHERRY_OUTPUT outputs['durian_output'] = basePath + FruitConstants.DURIAN_OUTPUT return outputsAnd no, the FruitConstants are never used anywhere outside this method.
Re: Coding
Date: 2025-07-25 03:30 am (UTC)class FruitMetrics: """ Increment a counter metric """ def incrementMetric(metricTag, value): if metricTag in counters: counters[metricTag] += value else: counters[metricTag] = value """ Increment a counter metric by 1 """ def incrementMetric(metricTag): incrementMetric(metricTag, 1)Re: Coding
Date: 2025-07-25 08:18 am (UTC)Re: Coding
Date: 2025-07-25 08:24 am (UTC)Re: Coding
Date: 2025-07-25 06:43 pm (UTC)Of the other two, one of them is also offshore, and the other is an AI enthusiast. One of the files in this PR is a Cursor prompt he accidentally checked in.
Re: Coding
Date: 2025-07-25 07:11 pm (UTC)Re: Coding
Date: 2025-07-25 03:32 am (UTC)Re: Coding
Date: 2025-07-25 05:02 am (UTC)Re: Coding
Date: 2025-07-25 05:57 pm (UTC)Re: Coding
Date: 2025-07-31 10:14 pm (UTC)And guess what our AI-obsessed engineer did? He replied with a thumbs-up and then added a new .cursor file with instructions using my exact wording. I am so tired.
Re: Coding
Date: 2025-07-31 10:14 pm (UTC)Re: Coding
Date: 2025-08-01 11:00 am (UTC)Re: Coding
From: (Anonymous) - Date: 2025-08-01 11:19 pm (UTC) - ExpandRe: Coding
From: (Anonymous) - Date: 2025-08-01 11:40 pm (UTC) - ExpandRe: Coding
From: (Anonymous) - Date: 2025-08-01 11:47 pm (UTC) - ExpandRe: Coding
From: (Anonymous) - Date: 2025-08-02 12:03 am (UTC) - ExpandRe: Coding
Date: 2025-08-05 03:27 am (UTC)Re: Coding
Date: 2025-08-05 03:34 am (UTC)Re: Coding
From: (Anonymous) - Date: 2025-08-05 03:37 am (UTC) - ExpandRe: Coding
Date: 2025-08-05 03:49 am (UTC)Was told to my comments had been addressed and that this PR was, once again, ready for review.
The unnecessary methods I complained about have now been marked deprecated. No additional changes have been made. ✨ The code in this PR was deprecated before it was even merged, which I think is a new record.
Re: Coding
From:Re: Coding
From: (Anonymous) - Date: 2025-08-05 04:01 am (UTC) - ExpandRe: Coding
Date: 2025-08-05 04:01 am (UTC)Re: Coding
Date: 2025-08-05 03:33 am (UTC)Re: Coding - MODS
Date: 2025-08-05 03:42 am (UTC)Re: Coding - MODS
Date: 2025-08-05 03:47 am (UTC)Re: Coding
Date: 2025-12-03 07:33 pm (UTC)Re: Coding
Date: 2025-12-03 07:45 pm (UTC)Re: Coding
Date: 2025-12-03 08:09 pm (UTC)Re: Coding
From: (Anonymous) - Date: 2025-12-03 08:22 pm (UTC) - ExpandRe: Coding
Date: 2025-12-04 06:33 pm (UTC)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
Date: 2025-12-04 07:12 pm (UTC)Now that's the kind of logging that every enterprise needs. Ship it!
Re: Coding
From: (Anonymous) - Date: 2025-12-04 08:23 pm (UTC) - Expand