Sample
JetBrains/b43
Human rating uses the original dataset scale.
Scores
| Method | Score | Scale | Dataset rank (0–100) |
|---|---|---|---|
| Posnett | 0.524 | 0–1; higher is more readable | 100.0Δ 12.3 |
| Scalabrino | 0.939 | 0–1; higher is more readable | 93.2Δ 5.5 |
| Dorn | 0.547 | 0–1; higher is more readable | 56.8Δ 30.9 |
| Mi | 0.468 | 0–1; higher is more readable | 45.8Δ 41.9 |
| LLOC | 4 | Logical lines; fewer is more readable | 92.8Δ 5.1 |
| DeepSeek V4 Pro | 18.33 | 0–20; mean of three runs | 97.9Δ 10.2 |
| GPT-6.1 Sol | 19 | 0–20; mean of three runs | 96.2Δ 8.5 |
| BTTF | 0.639 | 0–1; higher is more readable | 93.2Δ 5.5 |
| Human | 0.94 | 0–1; original rating | 87.7 |
Views
Loading feature diagnosis…
Source regions
Feature contributions
Feature contributions
| Feature | Value | Contribution (log-odds) |
|---|---|---|
| Halstead volumeHow much symbolic information the code contains. It combines the total number of operators and values with the number of distinct ones. | 310 | −10.23 |
| Source linesThe number of non-empty source lines. | 18 | +7.2 |
| Byte entropyHow varied the bytes in the source text are. Repeated bytes give a lower value; a more even mixture gives a higher value. | 3.829 | −5.743 |
Intercept 8.87 + feature contributions = 0.097 (log-odds).
Score = sigmoid(0.097) = 0.524.
| Score | 0.939 |
|---|
Feature contributions
| Feature | Value | Contribution (log-odds) |
|---|---|---|
| Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right. | 0 | −0.804 |
| Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *. | 0.031 | +0.637 |
| Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code. | 18 | +0.399 |
| Number layout frequencyHow rapidly the number of numeric values per line changes through the code. | 1 | +0.398 |
| Indentation frequencyHow rapidly indentation changes from line to line. | 16 | −0.184 |
| Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom. | 16.308 | −0.182 |
| Identifier layout (horizontal)How rapidly the visual pattern of identifier characters changes from left to right. It measures spatial frequency, not the meaning of the names. | 90 | −0.147 |
Intercept 0.07 + feature contributions = 0.187 (log-odds).
Score = sigmoid(0.187) = 0.547.
| Score | 0.468 |
|---|
| Score | 4 |
|---|
Run 1
The code is highly readable. It has a clear, logical structure with a single class and main method. Nesting is minimal, with no conditional or loop nesting. Intent is obvious: print three tongue twisters. Code length is appropriate for the task. Each System.out.println call is split across multiple lines using string concatenation, keeping line lengths reasonable and the reading flow natural. Action granularity is good—each major output is a separate statement. Minor room for improvement could come from using text blocks (Java 15+) to reduce concatenation, but the current style is clean and consistent.
Run 2
The code is highly readable. Structure is logical with a single class and one clear method. Nesting is minimal, with only class and method level indentation. Intent is immediately clear—printing tongue twisters. Length is concise and purposeful. Action granularity is good, with each print statement logically grouped across lines. Reading flow is natural, following the sequence of output. Minor formatting inconsistency exists (mixed use of line continuations and blank lines), but overall it is clean, simple, and easily understood.
Run 3
The code is very readable. It follows a clear, logical structure: a single class with a single main method that sequentially prints three tongue twisters. Nesting is minimal, with no conditional or loop constructs. The intent is obvious from the class and method names. Code length is concise and appropriate for the task. Each println statement represents a distinct action, though each spans multiple lines due to string concatenation, which actually improves readability by keeping lines short and logically grouped. Reading flow is natural, moving from one tongue twister to the next. Minor deductions could be made for slight inconsistency in line breaks/spacing, but overall it is highly readable.
Run 1
Code Structure: Logically organized into a single class and main method, with blank lines separating the three tongue twisters. Nesting: Minimal, consisting only of the necessary class and method scopes. Clarity of intent: The class name and straightforward print statements clearly communicate the purpose. Code length: Concise for the output produced, with no unnecessary logic. Action granularity: Each statement performs one printing action; splitting string concatenations across lines improves readability. Reading flow: Natural top-to-bottom execution, with consistent indentation and string alignment. A minor inconsistency in trailing newlines between the first two outputs and the last slightly reduces uniformity.
Run 2
Code Structure: A single class and main method logically group three clearly separated output statements. Nesting: Only the necessary class and method levels are present. Clarity of intent: The descriptive class name and straightforward print statements clearly convey the purpose of displaying tongue twisters. Code length: Concise for the task, with no unnecessary abstractions or logic. Action granularity: Each statement performs one output action; splitting concatenated strings across lines keeps the text readable. Reading flow: Consistent indentation, aligned string continuations, and blank lines create a natural top-to-bottom flow. Minor drawback: Explicit newline escapes and concatenation add visual clutter compared with Java text blocks.
Run 3
Code Structure: A single class and main method logically group three distinct output statements. Nesting: Only the necessary class and method levels are present. Clarity of intent: The class name and explicit print statements clearly communicate that the program displays tongue twisters. Code length: Concise, with string literals split into manageable lines rather than unnecessarily expanded. Action granularity: Each statement performs one output action; continuation lines only concatenate text. Reading flow: Consistent indentation, aligned strings, and blank lines between tongue twisters make the code easy to follow. Minor drawback: Embedded newline escapes and concatenation slightly increase visual clutter.