r/java • • 2d ago

Telltale signs of Vibecoding in Java?

Someone recently flagged one of my mods as being "obviously vibecoded" (which it wasn't), so I appealed the decision. just out of curiosity, what exactly are the signs people are seeing when accusing code of being vibecoded?

76 Upvotes

138 comments sorted by

61

u/Ok_Option_3 2d ago
  • Comments saying what the code does not do. 
  • Comments that repeat themselves
  • Vast amount of code with no comments at all
  • Excessively complex clauses all in one statement
  • Flat class structures, where inner classes might make more sense

The tells are the same in all languages.

70

u/xyzsomething 2d ago

"Vast amount of code with no comments at all" ... that's a lot of Java code bases I've seen before 2020, I would actually say the opposite is true, the more comments the more signs it is vibe coded.

"Excessively complex clauses all in one statement"... again I've seen this a lot in very old pre vibe-coding code bases, you have to remember that LLMs are just imitating us.

8

u/Ok_Option_3 2d ago

That's why they are AI tells - not 100% certain proof that AI was involved.

3

u/Wonderful-Habit-139 1d ago

The funniest part is seeing people that use AI, get caught using AI, and then they start telling you things like this. Even though they have already being caught lol.

2

u/-illusoryMechanist 18h ago

I guess I'm an llm because i put probably an excesisve amount if comments in my code

1

u/koflerdavid 1d ago

Calling this out is still worthwhile when you get such submissions from people who are usually not working like that.

14

u/john16384 1d ago

History lessons. Claude tends to include things in comments or javadoc for how things used to work, or things that were tried during a coding session but rejected. I have to keep telling it to document how things currently work and to skip the history lessons. This is also the reason why I really dislike people that tend to make 5000 commits for one feature, as if all that is actually relevant when it is just back and forth changes.

1

u/The8flux 1d ago

I do 1700 tests then commit after a green gate. At every gate

1

u/thingerish 1d ago

This exactly. Before I added explicit and extensive rules about that it would tend to capture all the iterative design discussion in comments. We don't need that Claude buddy. We have design docs you know?

1

u/Aulodia 2d ago

i *very* rarely add comments so this explains alot lol

7

u/dad_farts 1d ago

Excessively complex clauses all in one statement

My style being called out

19

u/barcodez 2d ago

This just sounds like most code written by humans. AI on the other hand adds comments, and generally keeps to good clean design in my experience.

12

u/Head_Evening_5697 1d ago

No. Humans (rarely?) never add comments saying what the code does not do.

6

u/slaymaker1907 1d ago

I'll add it if there's a non-obvious answer why something wasn't done a particular way.

2

u/LelouBil 1d ago

Of course, but that's more of an explanation on why the code is like this.

if you vibe code and don't care you will end up with comments like.

// This methods now only returns the full name of the user, and not the first name only like in the old behaviour.

Basically comments that don't explain the state of the code as it is now (or why is it like this), but explain how it was before. Which is not the point of comments.

5

u/eboob1179 1d ago

I like to screw with people in code review to see if they're paying attention. I leave comments like "//We've been trying to reach you about your car's extended warranty."

1

u/Zatujit 11h ago

so the problem is that people don't do things properly?

1

u/xvillifyx 1d ago

No?

Humans often modify code and forget to update the comments, leading to comments describing what the code does not do

9

u/vowelqueue 1d ago

I’ve mostly used Claude and feel that by default it goes really overboard with comments. You can definitely rein it in but a lot of people don’t do that and it’s very easy to tell what code was written with AI by its commenting style.

7

u/_predator_ 1d ago

It's like websites and frontends. You can immediately tell when Claude was used to create them, which is ironic given how simple it would be to avoid it with some small instructions related to styling and font choice.

3

u/coderemover 2d ago

No it doesn’t keep the code clean. It has a very bad taste at how to decompose problems into smaller ones.

0

u/barcodez 1d ago

righto

2

u/Greenix 1d ago

Comments and clean design in the same sentence is an oxymoron.

1

u/The8flux 1d ago

It's the best typewriter I have ever used.

1

u/Wonderful-Habit-139 1d ago

> adds comments

This is not a measure of "good clean design".

3

u/katieglamer 1d ago

I am so bad at adding comments to my code, and do leave myself notes saying what things don't do like // I'm going to need to deal with this thing so it doesn't break the other thing. But what I write is so unhiged I doubt anyone would think it's AI

2

u/Kwese_ 1d ago

Flat class structures, where inner classes might make more sense

In my experience it's the complete opposite. AI loooves to extract things into separate classes, be it inner classes or just regular classes, even when it makes no sense at all.

What I would add: AI also loves to put everything in a helper function. I've seen AI extract Boolean.TRUE.equals(x) into a isTrue(x) helper function.

2

u/Zatujit 11h ago

"I've seen AI extract Boolean.TRUE.equals(x) into a isTrue(x) helper function" tbf sometimes i do thins like this

3

u/Electrical_Being_813 1d ago

Ai comments actually say what function does. Unlike human

3

u/koflerdavid 1d ago

As long as somebody bothers to keep them in sync whenever the code changes in the future...

1

u/agentoutlier 1d ago

Oof... except for that first one and maybe that last one my code falls in to a lot of that I think although I'm not sure about the clause one.

1

u/Revanchan 21h ago

I have very bad commenting habits (to my own detriment) so I usually have huge blocks of code not commented at all.

1

u/monocasa 19h ago

That just sounds like corporate code.

1

u/thunderbird89 3h ago

Vast amount of code with no comments at all

That can also be an indication of human-written code. Some people are averse to comments.

5

u/Designer_Storm8869 1d ago

The easiest way is checking the last modification date. If it's from 2026, you have 100% certainty it's vibecoded

126

u/repeating_bears 2d ago

Adding to what others said:

More tests than any sane human would write, LLM language in README / comments, few git commits, which are massive in size

11

u/raelik777 1d ago

The tests and LLM language are the biggest tipoff. I'm personally guilty of massive commits though, no AI required 🤣 Typically one huge commit followed by a bunch of tiny one-liners where I'm fixing shit I missed.

32

u/CorrectProgrammer 1d ago

Add to that tests no sane human would write.

15

u/DGC_David 1d ago

Lol I have seen some wild shit in tests on the enterprise level.

11

u/fluffytme 1d ago

Yeah same here. We have some legacy apps with many thousands of tests each, all hand written

3

u/shorns_username 14h ago

tests no sane human would write

You overestimate (underestimate?) humanity. Or at least, your definition of "sane" is wishful thinking.

Once saw hundreds (actually probably thousands) of tests that had been written to test every getter/setter in the app.

The code looked like something like:

public void testXxxGetYyy(){
}

Literally a bajillion test methods, to test manipulator methods... with no implementation.

And those'd been there for years before I started working on the project, which many allegedly sane humans had worked on.

1

u/DGC_David 14h ago

That's what I'm saying... I once saw a test that checked the Value of a const... I think the og forgot to change but idk what they were saying

17

u/chabala 1d ago edited 1d ago

As someone who still tries to do TDD, it pains me that this is becoming the criterion.

Not that I could convince my peers to write any tests at all without LLMs doing the work for them.

13

u/hazel-blur 1d ago

I have my Agent do TDD. That however often leads to thing like

"Remove that icon"

"Ok, I first write a test asserting the absence of that specific icon..."

6

u/katieglamer 1d ago

Me over here forgetting to commit for 3 weeks

9

u/agentoutlier 1d ago

I confess I use LLMs for writing tests. (mostly) Worse case it is fuzz. It can get especially crazy if you have them do mutation testing which I recommend for some tiny isolated places like a parser (again fuzz).

Also I force them not write tests just to improve coverage and I have them try to write as close to possible permutation based end to end tests where I can overlook what the inputs and outputs are.

4

u/thephotoman 1d ago

Oh, I’ve done more tests than sane humans would write by hand out of malicious compliance before.

4

u/Gwaptiva 2d ago

I am probably not a sane perdon, because unless I prompt Claude explicitly, it doesnt write tests

1

u/Urtehnoes 1d ago

Tests that just say assert true; return true;

Like OK maybe AI has reached human intelligence, because it's making tests my coworkers make!

0

u/findus_l 1d ago

The few git commit part I have seen before ai and I tell my agents to make small commits because I don't like big ones.

-9

u/emberko 1d ago

One of the things I'm grateful to AI for is that it killed the TDD shit now and forever.

6

u/space-bible 1d ago

It killed TDD?

1

u/repeating_bears 1d ago

TDD as a methodology is to write the tests before the impl, so that you learn what the interface should be, basically. There are not many people prompting an LLM to write the tests before the impl. It all gets done together. (tbf there were not many people doing "true TDD" before AI either)

2

u/Tasorodri 1d ago

I've specifically seen a lot of people that work extensively with an agentic workflow to specifically have the agents work in TDD.

1

u/bitspace 1d ago

I don't even have to prompt it to - literally every model I use now starts with red tests.

2

u/Rasutoerikusa 1d ago

? I've seen the opposite where humans write and specify tests, after which llm implements it according to it. At least I've seen a new rise in TDD in the past year

2

u/koflerdavid 1d ago

Now you actually gave me an idea. Most people don't like TDD because writing tests sucks. They prefer to write the implementation. But how about letting the LLM write tests only and thus isolate the slop to the test suite?

220

u/java-with-pointers 2d ago

A lot of comments, comments on code that was deleted explaining why it was deleted, lack of reusability

43

u/7Roses 1d ago edited 1d ago

You just described the common signs of java legacy code 🤔 Edit: with the difference legacy code method names probably are some cryptic name that needed the comment for clarification

21

u/java-with-pointers 1d ago

Legacy code can mean a lot of things but I've worked with quite a few such codebases and they never looked like that.

4

u/koflerdavid 1d ago

Already a 3:1 relationship between comments and code would be a dream for legacy code. Now, those comments are actually not always immediately useful since people might have forgotten to keep them all in sync with what is actually going on, but it is telling something, and commit history would make it possible to unravel that wall of graffiti.

2

u/vytah 20h ago

That's why many people say LLMs are tools for instantly creating technical debt.

12

u/Wonderful-Habit-139 1d ago

Lmao, bonus points when it's deleted code in a PR that wasn't merged to main yet. Like why are you adding in a changelog something that only existed in a branch and never in the main branch? Sigh...

-9

u/majeric 1d ago

Well written, well commented code… vibe coding sounds horrific.

2

u/java-with-pointers 19h ago

Whats horrific is you assume there's nothing more to programming than writing code that looks good at a glance

1

u/majeric 11h ago

What’s more horrific is your transparent strawman fallacy. I never said “at a glance”.

In my experience, LLMs like Claude Opus 5.5 perfectly capable of writing clean, clear code.

43

u/it_happened_lol 1d ago edited 1d ago

Stateful comments that address the prompter and not the reader of the code. Some examples that come to mind:

// This gives you the biggest gain
(A.I agent addressing a developer who asked for more test coverage)

// Phase 2 of JIRA-4151 is resolved here, merge after JIRA-9415, blah blah...
(Describing a coordination plan in the comments that has already been completed)

19

u/_predator_ 1d ago

Recently started in a large org where they, let's say, embrace agentic coding. All code bases are full to the brim with your second example. Of course only the original author knows what those "phases" were.

What's funny is that agents will not fix or remove such dead comments unless you tell them to. So this crap keeps accumulating over time.

36

u/Frestyla 2d ago

2 line code change, 20 tests added

2

u/lordheart 1d ago

To be fair it might be a code base that had abysmal testing and some used the change to add some broad tests while they were there

15

u/da_supreme_patriarch 1d ago

Comments where they don't belong(on dependency imports, build files etc.) javadocs that are just "uncamelcasing" a field or method argument(like @angularAcceleration - the angular acceleration) or just the exact method name in plane English, tautological and heavily coupled to the actual code unit tests(test code checks that the code executes exactly as written, even the slightest deviations in actual code will break the test regardless of what the change is, eve if the program's logic is unaffected), unit tests for toString implementations of random classes where the toString would only affect the logs, random "javascriptisms", a few utils classes even when apache commons, guava or spring are in the classpath, code that is extremely paranoid about null-checking, not using java.time classes for date handling even when the JDK is well above 8, disdain for Optional-s, limited use of records and sealed types(this is a problem specifically with OpenAI models, Claude is somewhat ok here), not using lombok when it's in the classpath and is actively used, randomly introducing lombok to a project that doesn't use it, and a few other things

3

u/Spandian 1d ago

javadocs that are just "uncamelcasing" a field or method argument(like @angularAcceleration - the angular acceleration

That's not an AI thing... IDEs have been able to put boilerplate comments on everything for decades.

7

u/da_supreme_patriarch 1d ago

Correct, but that's completely useless by itself and is supposed to just be a scaffolding for the actual docs, a human doesn't really leave the autogenerated docs in the ide-generated state unless there is nothing to document, but the project rules require every public API to be have javadocs, and as far as I am aware not many projects do that

2

u/koflerdavid 1d ago

And LLMs have learned to reproduce that instead of inferring what the purpose of the field is.

2

u/vytah 20h ago
/**
 * Sets the up
 */
public void setUp() {

27

u/voronaam 1d ago

Another sign is unit tests that "hug" the code really close.

I once had a one-liner that changes default value of some flag in the application from true to false - the PM changed their mind. The original code and tests were written by AI. Do you want to guess how many unit tests failed after this tiny change? I expected exactly one. Maximum two. I expected there to be a test for the default behavior that I'd need to update and a random unrelated test that relied on the default.

Failed tests: 6. All directly related to the default.

AI wrote the tests and assertions for:

  • When the value is missing, it is treated as true
  • When the value is false it is false
  • When the value is true it is true
  • When the value was missing and gets set to true it is true and no longer missing
  • When the value was missing and gets set to false it is false and no longer missing
  • When the value was set to false and is deleted it is true

No sane human would ever write that many tests for a trivial boolean flag. It was left configurable to begin with because the PM was not sure which way they want it It is not like we expected PM to be changing it back and forth all the time.

When changing 1 line of code leads to 40+ lines of unit test changes - the tests are "hugging" the code way too close.

AI loves doing that for some reason. I guess it was getting scored by the lines of code it produced...

6

u/Tiziano75775 1d ago

I usually ask to reach 80-90% coverage with as few tests as possible, it avoids to make too many tests for the same line

3

u/Zatujit 11h ago

isn't it the point of unit tests?

1

u/voronaam 2h ago

Not really. The point of unit tests is to cover the desired functionality, not to re-express the current implementation in assertions.

For example, if you have a "UserService", a good test might call a createUser method and then assert that getUserCount() == 1 and findUser(...) returns the creted users.

An AI-written test is quite likely to additionally reach straight into the DB with a couple of SELECT to assert the record is created in exactly the format it is done now, assert that a log line written as plaintext to a log file, assert that a metric usersCreated is emitted in Prometheus format, and also have a "no other interactions" assertion in the end.

Witch such a test and for no good reason it would be harder to switch from PostgreSQL to MongoDB, switch the loggers to structured format, add support for CloudWatch metrics or to literally add any functionality like queued up marketing events tied to user registration.

A human written tests cover the functionality that matters. If after creating a new user the total count of users is wrong - it is a bug. It is helpful to have a test that'd fail on it. The AI loves to write tests the cover everything else.

Another example is when the code has a bug. I've seen AI to find it - and happily cover it with a test. For example, human writing a test and finding out that "user names with a hyphen cause exception" would fix the exception. AI would write a test "hyphenated names are not allowed" - hugging the existing implementation insanely close, down to the exact bugs in it.

1

u/Yesterdave_ 1d ago

And have you found a strategy to get the AI to not do that?

2

u/voronaam 1d ago

Me personally? When I do story work, I just tell it to not write any tests until directed. And then I tell it which tests to write. When I do bugs, I like to do TDD. So there a single test written to reproduce the bug to begin with. No more tests added later on.

Note that it is not an "agentic" approach. I have seen so many people try and fail to get a bunch of Markdown files to make LLM behave differently. It never works.

9

u/ihatebeinganonymous 2d ago edited 2d ago

Maybe not strictly "vibe coded", but the Java code AI generated for me, even when it was "glorified autocomplete" and before Agents era, had a weird obsession with using "System.out.printf" instead of println. I had (almost) never seen or used printf in Java code before. 

3

u/koflerdavid 1d ago

I like to use it since creating nontrivial formatted output (f.ex. numbers with padding or in non-decimal formats) becomes quickly very annoying with just print and println.

1

u/ihatebeinganonymous 1d ago

For that type of formatting I use String::formatted, which again AI tends to avoid in favour of String concatenation whenever possible :<

2

u/koflerdavid 1d ago

Well, String::formatted is a rather new API...

7

u/akl78 2d ago

Long, grammatically correct and well-formatted comments.

6

u/iLoveCalculus314 2d ago

I noticed that vibe coded Java uses a ton of “resolver” classes. Also, brittle tests that use log capture to check for specific logs instead of validating the actual behavior.

5

u/Life_is_a_meme 1d ago

My favorite one at work is when somebody sends in a one line change that comes with four lines comment for what is an inconsequential update that needs no historical accountability.

My favorite is when the comment can go away if they just... name the variable better, but "they" in this case is Claude. Sloppy prompting.

4

u/tonetheman 2d ago

I used to see lots of weird spacing on the ends of lines... not sure that is still a thing though since things are changing so quickly

10

u/vips7L 2d ago

Defensive bullshit that no one should worry about. Like record constructors for dtos that copy collections. 

6

u/ukobg 2d ago

defensive copy can actually be useful no? I feel like the scenarios where it would break are not that edgy

2

u/vips7L 1d ago

Yes it’s useful if you’re worried about the hashcode of a record changing if you stuff them into sets. But when it’s a simple record for pushing data over a web response it makes absolutely no sense to defensive copy, especially if the whole object graph of the stuff in the collection isn’t immutable.  It’s only some an LLM will worry about. 

    return Response.ok()          .entity(new WhateverDto(list))          .build()

3

u/Milyardo 1d ago

Not using an immutable collection in a dto seems like the bigger issue an LLM would miss in those situations.

2

u/Cell-i-Zenit 1d ago

Defensive bullshit that no one should worry about. Like record constructors for dtos that copy collections.

alot of guards in a class for null etc, which were already ruled out earlier etc.

For example you have a relationship with hibernate and call parent.getChilds(), and the ai is doing a null check on that for some reason

7

u/EviIution 2d ago

Long method comments formatted with <p> for obvious methods. 

3

u/coderemover 2d ago

Just recently found some AI models notoriously nest try with resources inside try catch. They don’t seem to know you can flatten them.

3

u/Yes_Mans_Sky 1d ago

To be fair I always forget that you can put multiple declarations in one try block.

3

u/Deep_Age4643 1d ago

We let do AI do a big migration from Ruby to Java. When we inspected the generated code it made everything general objects, such as List<Object>. At the end we migrated on module by hand, and then it went better now it had an example for the other modules.

0

u/Fuzzy-System8568 1d ago

Is anyone else concerned we are literally teaching OP how to modify their project to make it look non-vibecoded?

1

u/koflerdavid 1d ago edited 1d ago

If OP takes out the LLM-isms and makes their code worse in the process then so be it.

Helping OP make their code better would also be a beneficial outcome because that's how one is supposed to work with LLM tools: iterate on what they produce instead of zero-shotting, or fix it up by hand, preferably both.

The issues with vibe coded code are the same as a talented junior developer's submission:

  • it works, at least in most cases, but nobody precisely understands why.
  • coding style is unmaintainable, overly verbous, puts priority on the wrong things, or generally doesn't fit to the rest of the project.
  • copypasta. Human developers tended to copy from StackOverflow, LLMs copy from everywhere.

-4

u/Aulodia 1d ago

did u even read the post???

4

u/Fuzzy-System8568 1d ago

Yes. I do not believe you.

3

u/Wonderful-Habit-139 1d ago

Yeah, pretty sure they got caught and even though they didn't fully "vibecode it" they definitely used LLMs a bit too much and it showed.

-4

u/Aulodia 1d ago

guess i have to delete the post everybody, fuzzy-system8568 thinks i’m lying

0

u/Fuzzy-System8568 1d ago

First honest thing you have said since doing the OP

2

u/mrn1 1d ago

Look at the files, agents.ms or claude.md or similar

6

u/_predator_ 1d ago

I will say that I started adding agent configs to my OSS projects because it's how I can actively influence the quality of PRs I get, not because I need them myself. It's a bit like linters and formatters, but you also get to have contributors follow your preferences WRT how to approach bugfixes, how to format commits, what to put in PR descriptions and stuff.

It feels a bit like socially acceptable remote code execution on steroids at times.

1

u/koflerdavid 1d ago

Indeed, I also think these files are a useful summary for human developers to get up to speed. The DEVELOP file and its friends tend to contain quality up-to-date content only in more busy projects, if they exist at all. Without such guidance everybody wastes time struggling to set up their development environment and ends up reinventing hacks to achieve some sort of productivity.

2

u/Ok_Entrepreneur_8509 1d ago

Comments describing 10 things that *don't* work to justify the solution.

2

u/kamran-zafar 1d ago

I'd be wary of any single tell, because the cosmetic ones (over-commenting, uniform naming) are also what a tidy junior or a tutorial-trained dev produces. The ones I find more telling are about behaviour not style.

- Error handling that swallow and carries on or an empty default, so failures are silent.

- Null/empty checks everywhere

- Abstractions with exactly one implementation, plus helpers that do nothing much.

But none of that proves anything and plenty of hand written code does the same. If youre appealing, I'd point to your commit history and the design decisions you can explain, since that's much harder to dispute than a vibe.

4

u/s0ftware-dev 2d ago

Full class path of types instead of importing. 

3

u/chewyfruitloop 1d ago

Comment blocks with over use of highlight values e.g. instead of saying true you get {@code true}
Preference for ternary operations
Inability to decompose class into something readable
Documentation on a class that’s repeated in the code
Word salad in docs
Inability to use anything newer than Java 14 because it’s not seen enough of it

8

u/_predator_ 1d ago

I've been doing the {@code} thing for Javadoc since forever. I may be a bit hyper-fixated on pretty formatting though.

2

u/chewyfruitloop 1d ago

Oh you’re the one it learned it from! 🤣

2

u/Raedwald-Bretwalda 1d ago

This is like em-dashes. Carefully produced professional documents used em-dashes, but typical good-enough documents did not, so the Plagiarism Machines learned em-dashes as a marker of quality. Now those of us who did take the care to use them can not any longer.

1

u/Jonjolt 1d ago

One of my copywriters that I hire uses em-dashes a lot, I'm face palming myself people going to think everything he wrote was AI slop 🤦‍♂️

3

u/Wonderful-Habit-139 1d ago

> "obviously vibecoded" (which it wasn't)

It wasn't "obviously vibecoded", but you used LLMs didn't you? If you were caught and you did use LLMs, who are you trying to convince?

2

u/microbit262 1d ago

There is a difference in vibecoding the whole logic and using AI to add stuff like comments or tests without letting it make changes to the logic itself.

Both used AI to some capacity, but it's a difference when the human still writes the main algorithm and logic

4

u/Wonderful-Habit-139 1d ago

I don't understand the point of telling me this when they have been caught using AI to generate code? Obviously something has gone wrong when they can tell that you used AI (Not you specifically just a general "you").

It's just the will smith meme all over again. "Just because it looks like it's AI generated doesn't mean it is AI generated! Well, I did AI generate this... but not because it looks like it!" ._.

2

u/BoredGuy2007 1d ago

It works & isn't covered in Java 8 bloodstains from a decade ago

1

u/wakingupfan 1d ago

Use of the |= operator in a loop

1

u/SlaminSammons 1d ago

So I haven’t really seen this, but I find that AI code loves to make every single method static.

1

u/Suspicious-Walk-815 1d ago

a lots of junits for the given code yet doesnt cover whole branching with test data !
adding complex new implementation instead of following existing patterns

1

u/frandevme 1d ago

When the person never added any Javac, and now, out of nowhere, the start addind it

1

u/dvayanu 1d ago

Higher then usual quality, ton of tests, readable commit messages with a lot of text and actual explanation, Claude as co-author

1

u/Alarmed-Tell1315 1d ago

I don’t think there is one clearer than the style and density of comments. The code itself is as good or bad as human written code, specially with a good harness, it’s mostly undistinguishable nowadays.

So, someone telling you it’s vibe coded it’s telling you he thinks it’s bad code, and if no specifics are provided as follow up, you should ignore the comment.

4

u/Wonderful-Habit-139 1d ago

> The code itself is as good or bad as human written code

Not true.

> it’s telling you he thinks it’s bad code

Not true. Bad human code is different from bad AI code.

1

u/Alarmed-Tell1315 1d ago

In what ways, can you be specific? This are demonstrable facts, not my opinion.

Read the study titled: Human-Written vs. AI-Generated Code: A Large-Scale Study of Defects, Vulnerabilities, and Complexity

Human code tends to have more complex failure profiles, have less repeated code, have more unused constructs, less hardcoded debugging, more maintainability issues,and have almost identical vulnerabilities, compared to LLM generated code.

Average quality is about the same, the problem is not generated code, the problem nowadays is cognitive debt (when humans stop understanding how the system works and hand everything to agents). But the code itself in average, is indistinguishable from human code unless meticulously analyzed.

1

u/chabala 1d ago

These tools are like a mirror, it makes what you allow it to make. If you don't know it looks like slop, you're making slop.

0

u/m39583 1d ago

There isn't anything remotely reliable.  I find by default it tends to add a lot of comments and the main tell is excessive verboseness. Also unit tests for absolutely everything, tests that no human would ever bother writing.

But you can tone all that down if you tell it to. 

This is the problem with accusing people of using AI, it's not accurate and it can be used to dismiss people without cause.

And what is the problem with using AI? I'm a software developer and it's utterly transformed our industry. I find people that object to it so weird, like do we look down on people that use IDEs and build tools rather than hand crafting their code with notepad and javac?

If someone has a good idea but isn't a developer then use it to try and deliver your idea!  It's not like humans write perfectly crafted artisan code

2

u/koflerdavid 1d ago edited 1d ago

do we look down on people that use IDEs and build tools rather than hand crafting their code with notepad and javac?

Yes, people do look down on developers who can't get anything done without an IDE. (Granted, the Java ecosystem does not make that easy) And it is a sign of unpolished code to find artefacts of being IDE generated, such as

} catch (AnUnhandledException e) {
    // TODO Auto-generated catch block
    e.printStackTrace();
}

The conveniences of IDEs are necessary to get things done nowadays, but one can argue that's because of bloated systems that could only be built with the help of IDEs in the first place. A similar lesson has been learned by many open source projects - they now have to use LLMs to deal with the flood of LLM-generated submissions coming in.

If someone has a good idea but isn't a developer then use it to try and deliver your idea! It's not like humans write perfectly crafted artisan code

That's a strawman - nobody has ever argued human generated code is better because all of it is perfectly crafted artisan code. Far from it. But humans improve as developers and gain an understanding of the domain as they write code, and evaluating and editing LLM-generated code is just not the same. LLM slop is looked down on because it is unmaintainable, and having to use an LLM to deal with it sounds like a waste of tokens.

-1

u/hippydipster 1d ago

Really well-written code that works, is well-documented, and supported by tests.

0

u/regjoe13 1d ago

“Therefore, it was agreed, compilers could only turn out code which would be intolerably less efficient than human coding”

1964, John W. Backus and W. P. Heising, FORTRAN

-4

u/JustADirtyLurker 1d ago

The vast majority of comments I am reading seem like was written 12 months ago.

My experience with Claude or Kimi is not hitting any of these tells. Code agents have become pretty good to be honest.

-3

u/Misophist_1 1d ago edited 1d ago

I started to use that s*t just recently, and am likely a bit behind the curve, but was recently ostracised für using AI for *generating* a reddit-Post, when in fact I did not - but mentioned that I used AI to research for the topic at hand.

My take is, that it is increasingly hard to tell, especially when developers start to form and direct the AIs output with specially constructed skills, modify and retrofit existing code, and on top of it, use Sonar and Spotless to enforce coding conventions and quality criteria.

I'm with Torvald's approach there. AI is or will become just another tool. But the old adage: 'A fool with a tool is still a fool' hasn't gone away. Wether the code is any good, isn't just depending on the AI. It is depending on the programmer putting it to use, the craftsman knowing the limitations of the tools he uses.

It is OK to shame bad code. But it should be shamed, because it is bad, regardless of the use of AI, not because of the use of the AI.

If people are no longer able to see the difference, it may be because AI has managed to beat the Touring Test when writing code.

-5

u/geodebug 1d ago

Who cares if it is vibe coded as long as you agree with and understand the output?

I’m a software engineer of 30+ years and barely write code by hand anymore. But I don’t just “trust it”.