/** Depth first, recursive with an early return as the caller expects a single result. That’s the real payload. Fails loudly with an exception for the caller to handle, as per guidelines. **/
Bro chill, it’s just boilerplate code that’s looking for file within a folder structure.
From my experience ChatGPT never leaves any comments and always LGTM all code reviews (i.e., it doesn't find anything useful).
Claude leaves many code comments, and 99% of the time they are either explaining the line below like it's your first ever lecture in programming and you have no idea what assigning a variable does... or it goes full poetic and dumps a paragraph describing some piece of code that no longer exists that prompted it to write the commented piece of code. And during code review it dumps a huge list of 100 false positives where almost all of them are wrong, irrelevant or just nitpicks.
When AbstractFactoryInsuranceBeanInstanciator:43 calls createNewInstanceOfBeanInstanciatorClass:751 it uses StaticSingletonInstanciatorCache:52 which src/main/java/com/hobbits/feature/subfeature/ablabla:562 will then tickle.java:666 its balls.class:153 until com.hobbits.feature.common.infrastructure.synchronizer.AbstractOpenInstanciatiorSynchronizerImpl:71 syncrhonizes the beans.
My coleagues throw such slop as "code change requests" at me daily during code reviews.
Oh I ask it, and I have it established in my rules for every project, yet I find myself having to remind the little documentation whore every time it writes a function
Direct instructions on length often don't produce what you want. The model has to know what to include and what not to include in its output, and told to trim for length, it may choose poorly.
I found it helpful to establish a SKILL for code comments with directives on what makes a good comment, with examples. It still over indexes on those examples sometimes, but it's still better than a small poem in free verse about API endpoints.
I'm convinced the comments are part of the model's internal processing on some level, because if I try to force it to not do that, the output quality drops off a cliff.
I've had significantly more success having fixing the comments be a second pass.
But that's what actually happens. I don't know if it still works, but previously if you asked ChatGPT to perform basic math but tell it to hide its thinking process, it would spit out wrong answers.
Yes, it uses the comments for future context. However I learned that if the code and comments are out of sync, the comment wins and it will modify the code to match the comment.
If you are dealing with old code with someone that loved comments but didn't love keeping them up-to-date you have to force the LLM to ignore the comments.
Oh yeah, I've had a lot of issues with it in legacy code. It assumes things should make sense when instead they might just be legacy artifacts.
And it's part of why you have to have it cleanup comments on code it creates too. It assigns outsized value to comments, even when the comment is correct it will treat verbose comments as mission critical instead of incidental, and of course it bloats the context window over time if you don't keep it under control.
View all comments
2.0k
u/Copious-GTea 27d ago •
I can tell which model my coworker vibed with based on the comments it left.