AI PR adds auto generated comments to whole Spring Boot Project

Comments that say HOW commonly useless, as that is almost always self-evident (i.e. &quot;just read the code.&quot;). Comments that explain WHY are worth their weight in gold, and not something AI could ever create.<p>For example:<p><pre><code> &#x2F;&#x2F; How: This filters records by MyType of J and if they have children &#x2F;&#x2F; Why: We want Jobs (J) when those Jobs have Children. Otherwise, we&#x27;ll get JobGroups or Jobs without any Children we need to process below. .Where(T =&gt; T.MyType == &quot;J&quot; &amp;&amp; T.Child.Count() &gt; 0); </code></pre> WHY are, by their very nature, business rules or explaining a thought process. If the original developer of the code moves on or is unavailable, that information can sometimes not be found elsewhere.

As said in the PR comments, this is Codemaker AI advertisement, no good will.<p>And funnily enough, bad advertisement. How could a startup that focuses on code think that making a PR with 3,158 changed files is acceptable?

Ironically, it would&#x27;ve been more useful, and more inline with how non-trivial advancements in AI have been, to identify useless and obvious comments, and eliminate them.<p>I just experimented a little bit, and telling chatgpt to assume a self-documenting approach and skipping comments whenever possible, gets a pretty minimalist output. Add on asking about what non-obvious aspects might be noteworthy based on other projects, and I bet chatgpt would be able to find a list of things to look for, see if it&#x27;s applicable, and then rewrite in the appropriate format. Like if the function is about sorting, it could figure out that knowing if it&#x27;s stable is an important marker, and figure that out. Something like that could be useful.

Given that all the comments I&#x27;m seeing are of the “‘makeFooReady’ makes foo ready” ilk, I wonder how these tools fare on incorrectly-named things. Would it pick up on ‘asyncRemoveFoo’ being neither async nor a function that removes foo?

I struggle to see how any open-source project would accept this kind os PRs, the tools seems ok for research, but not a good ideia to push PRs like that open source projects.

I&#x27;m curious what the PR description means by &quot;the tool reached a compilation success rate of 99.9%&quot;. Did it break the code and introduce compilation failures when adding the useless comments?

To be honest, I see two positives regarding what Codemaker has provided here.<p>One is that (glancing through the comments) they&#x27;re actually significantly more thorough than what is already there and they&#x27;re at the level of thoroughness that a new user may actually want. Phil Webb is quite right; this <i>is</i> the level of detail someone new to the codebase could use, and if you could generate it dynamically on the fly as a &quot;Help me understand what I&#x27;m looking at&quot; tool that&#x27;d be really nice-to-have.<p>Second: I&#x27;ve <i>definitely</i> worked at places so tight-ass about code documentation that they <i>do</i> want &quot;makeAppleRed(): Makes the apple red.&quot; Mostly because they&#x27;re using doc engines that do a bad job of letting you know a function exists at all if it isn&#x27;t documented. I have no doubt Codemaker is going to make its money on those places.

This sort of AI-generated code context seems like it would be better as a VS Code extension rather than in code.

Serious questions: for those of you who say &quot;just read the code&quot;, don&#x27;t you find it useful when your IDE autocompletes what a function does? I do. And sometimes you can&#x27;t even read the code!<p>Note: I&#x27;m not talking about things that you know just by looking at the method itself, but things that are obvious when reading the code of the method only.<p><pre><code> &#x2F;** This will return the data *&#x2F; Data getData() {...} </code></pre> This is useless, But<p><pre><code> &#x2F;** This will return true iff it&#x27;s not empty *&#x2F; boolean isValid() {return !empty();} </code></pre> This is useful. This is what a good documentation should provide, and having documentation in the code itself (that you can later extract to an html page or other) is way better than having it on a separate platform that you need to remember to update.<p>Edit: remember that this is library that other people will use, it&#x27;s not an internal tool that only your team knows about.