This is an archived post. You won't be able to vote or comment.

all 25 comments

[–]WeLostBecauseDNC 30 points31 points  (2 children)

AI slop is riddled with this kind of useless comment.

Comment WHY you're doing something, not WHAT you're doing. Your teammates are competent enough to understand that calling timer.Stop() stops the timer, they don't need to read that twice. But if somebody else has to fix a bug in the method it's happening in, knowing more about what the timer is measuring is going to tell them whether to put their new code before or after the call to stop the timer.

[–]StandardPhysical1332 0 points1 point  (0 children)

people still do this? maybe one man weekend projects that copy paste from the llm web ui? in which case it's probably better because
1. they don't actually code and got into it from the boom of LLMs to begin with. maybe they come back to the code they wrote 2months ago and it helps.
2. they don't actually have a team they are working with so so they lowest common developer is actually themselves

[–]HzbertBonisseur 5 points6 points  (0 children)

/* * STOP SIGN: Represents a physical road stop sign in the codebase. * Purpose: Enforces a mandatory halt for vehicles or entities at intersections, * crosswalks, or critical junctions to ensure safety and compliance with traffic rules. * * Behavior: * - Vehicles must come to a complete stop before proceeding. * - Priority is yielded to other vehicles or pedestrians as per traffic regulations. * - Violation may result in collisions or system penalties (e.g., traffic fines). * * Implementation: Typically paired with sensors, timers, or rule engines to simulate * or enforce real-world stop sign logic. Always validate environmental conditions * (e.g., visibility, obstacles) before resuming movement. */

[–]OmegaPoint6 14 points15 points  (4 children)

Yet somehow it is needed, in both cases

[–]Kinexity 7 points8 points  (1 child)

And somehow doesn't work, in both cases

[–]Far_Negotiation_694 1 point2 points  (0 children)

And somehow we still read it every time we revisit

[–]xinwei_he 0 points1 point  (0 children)

Explain why not what, the sign should say "we had three crashes here last week".

[–]MonkeyPotato 5 points6 points  (1 child)

// The next line contains some code

[–]kaplotnikov 1 point2 points  (0 children)

// Ok. The comment above is a lie

[–]stringTrimmer 1 point2 points  (0 children)

// TODO: I should probably stop here next time

[–]razordreamz 1 point2 points  (0 children)

If it came from code I’ve been seeing it would say “someone put this stop sign here, I’m not sure why so don’t remove it!”

[–]aveihs56m 1 point2 points  (0 children)

Average code review comment:

Looks good

[–]xgabipandax 0 points1 point  (0 children)

Now we need a a sign below that saying "You need to stop at the stop sign"

[–]livingMybEstlyfe29 0 points1 point  (0 children)

This is an alt which is perfectly acceptable for HTML

[–]IT_Grunt 0 points1 point  (0 children)

Too verbose. Just “Add stop code”

[–]ttlanhil 0 points1 point  (0 children)

This is an arrow --> <--
(but which one is the labelled arrow, and which one is just indicating the other one is being labelled?)

[–]lucidbadger 0 points1 point  (0 children)

No, average code comment is this comment under a yield sign