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
61
u/Ok_Option_3 2d ago
The tells are the same in all languages.
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
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/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:
36
u/Frestyla 2d ago
2 line code change, 20 tests added
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
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
truetofalse- 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:
truefalseit isfalsetrueit istruetrueit istrueand no longer missingfalseit isfalseand no longer missingfalseand is deleted it istrueNo 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...
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.
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.
5
u/spyhunter99 1d ago
Emojis
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.
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/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?
2
u/mrn1 1d ago
Look at the files, agents.ms or claude.md or similar
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
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/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 loop1
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.
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
-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”.