Expand Cut Tags

No cut tags
[personal profile] hoisinsauce posting in [community profile] 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)
 
Depth: 1

Re: Coding

Date: 2025-07-25 03:17 am (UTC)
From: (Anonymous)
Stuck reviewing a 36-file PR full of utter slop. Look at this shit.

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 outputs


And no, the FruitConstants are never used anywhere outside this method.
Depth: 2

Re: Coding

Date: 2025-07-25 03:30 am (UTC)
From: (Anonymous)
There's another file that just contains this (well, this and twenty other constants that are also defined in another file). Why! Just why!

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)
Depth: 3

Re: Coding

Date: 2025-07-25 08:18 am (UTC)
From: (Anonymous)
Was this codebase in the hands of a team where LoC was treated as a metric? I've seen this kind of shit before when companies have contracted work out, to try to offshore dev jobs, and they've gone for the cheapest possible contractors who 1) don't know how to code and 2) are encouraged to write as many LoC as possible. You get this kind of code + meaningless comments, because there's usually a clause in the contract saying they have to comment every method.
Depth: 4

Re: Coding

Date: 2025-07-25 08:24 am (UTC)
From: (Anonymous)
And tbf, the other place you get this kind of code is me, when I am lazy. Well, no, not THIS bad and nonsensical, but looking at FruitIngester, I could see myself copy-pasting repeated lines in a stupid way if it was an early draft; I'd rather get code working and then make it Not Stupid, than work out how to abstract things when I'm tired. Though I'm also lazy, so in that situation FruitIngester wouldn't exist in the first place, because why tf does it exist.
Depth: 4

Re: Coding

Date: 2025-07-25 06:43 pm (UTC)
From: (Anonymous)
Ding ding ding! This PR has three authors, and one of them is a contractor from Cognizant.

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.
Depth: 5

Re: Coding

Date: 2025-07-25 07:11 pm (UTC)
From: (Anonymous)
How does this shit have THREE authors???
Depth: 2

Re: Coding

Date: 2025-07-25 03:32 am (UTC)
From: (Anonymous)
Also I forgot to pass 'self' into any of those class methods, oops. Well, now you know that this wasn't originally written in Python. It's been a while.
Depth: 2

Re: Coding

Date: 2025-07-25 05:02 am (UTC)
From: (Anonymous)
Did they vibe code this holy fuck
Depth: 3

Re: Coding

Date: 2025-07-25 05:57 pm (UTC)
From: (Anonymous)
Vibe coding can produce bad results but I don't think you'd see "if X: Y else Y" in code it produced. I agree it's probably an idiot trying to juice loc stats. I don't know what etiquette you have to follow but I would "just say no" to this nonsense.
Depth: 2

Re: Coding

Date: 2025-07-31 10:14 pm (UTC)
From: (Anonymous)
So, I ended up writing a 30-comment review that ended with a gentle reminder that other people will read and collaborate on this code, and that every additional line of code adds overhead for the next engineer.

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.
Depth: 3

Re: Coding

Date: 2025-07-31 10:14 pm (UTC)
From: (Anonymous)
Also, the PR is now 6.7k lines long.
Depth: 4

Re: Coding

Date: 2025-08-01 11:00 am (UTC)
From: (Anonymous)
I hope at least 5k is a short story, committed for flavour.
Depth: 5

Re: Coding

From: (Anonymous) - Date: 2025-08-01 11:19 pm (UTC) - Expand
Depth: 6

Re: Coding

From: (Anonymous) - Date: 2025-08-01 11:40 pm (UTC) - Expand
Depth: 7

Re: Coding

From: (Anonymous) - Date: 2025-08-01 11:47 pm (UTC) - Expand
Depth: 8

Re: Coding

From: (Anonymous) - Date: 2025-08-02 12:03 am (UTC) - Expand
Depth: 2(deleted comment)
Depth: 3

Re: Coding

Date: 2025-08-05 03:27 am (UTC)
From: (Anonymous)
aw fuck I didn't just accidentally ping someone to our den of iniquity and bad code right
Depth: 4

Re: Coding

Date: 2025-08-05 03:34 am (UTC)
From: (Anonymous)
I think you probably have. Keeps life interesting! I considered pinging mods but I don't think it'll wipe the notification if they have one. Dw is pretty dead anyway, mind.
Depth: 5

Re: Coding

From: (Anonymous) - Date: 2025-08-05 03:37 am (UTC) - Expand
Depth: 6

Re: Coding

From: (Anonymous) - Date: 2025-08-05 04:01 am (UTC) - Expand
Depth: 4

Re: Coding

Date: 2025-08-05 04:01 am (UTC)
From: (Anonymous)
Sounds like you might have gotten away with it, dan xD
Depth: 3

Re: Coding

Date: 2025-08-05 03:33 am (UTC)
From: (Anonymous)
Tell them that they can't jump straight to deprecated; they need to first include a deprecation warning for anyone using the project as it currently is, to give them time to adjust. 😈
Depth: 3

Re: Coding - MODS

Date: 2025-08-05 03:42 am (UTC)
From: (Anonymous)
Hello [personal profile] hoisinsauce does this notify you
Depth: 2

Re: Coding

Date: 2025-12-03 07:33 pm (UTC)
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.
Depth: 3

Re: Coding

Date: 2025-12-03 07:45 pm (UTC)
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.
Depth: 4

Re: Coding

Date: 2025-12-03 08:09 pm (UTC)
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.
Depth: 5

Re: Coding

From: (Anonymous) - Date: 2025-12-03 08:22 pm (UTC) - Expand
Depth: 3

Re: Coding

Date: 2025-12-04 06:33 pm (UTC)
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.
Depth: 4

Re: Coding

Date: 2025-12-04 07:12 pm (UTC)
From: (Anonymous)
> 📈 % of emails that contain the letter Y

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

Re: Coding

From: (Anonymous) - Date: 2025-12-04 08:23 pm (UTC) - Expand

Profile

secretfanspace: A happy spidermite, still forbidden, just without 'no' visible (Default)
Anon fandom messageboard

May 2025

M T W T F S S
   1234
567891011
12131415161718
19202122232425
2627282930 31 

Page Summary

Style Credit

Page generated Feb. 7th, 2026 12:39 pm
Powered by Dreamwidth Studios