Sample
JetBrains/e43
Human rating uses the original dataset scale.
Scores
| Method | Score | Scale | Dataset rank (0–100) |
|---|---|---|---|
| Posnett | 0 | 0–1; higher is more readable | 57.6Δ 27.1 |
| Scalabrino | 0.945 | 0–1; higher is more readable | 94.1Δ 9.3 |
| Dorn | 0.763 | 0–1; higher is more readable | 94.1Δ 9.3 |
| Mi | 0.209 | 0–1; higher is more readable | 14.4Δ 70.3 |
| LLOC | 13 | Logical lines; fewer is more readable | 52.1Δ 32.6 |
| DeepSeek V4 Pro | 18 | 0–20; mean of three runs | 94.5Δ 9.7 |
| GPT-6.1 Sol | 19 | 0–20; mean of three runs | 96.2Δ 11.4 |
| BTTF | 0.706 | 0–1; higher is more readable | 100.0Δ 15.3 |
| Human | 0.92 | 0–1; original rating | 84.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. | 619.275 | −20.436 |
| Source linesThe number of non-empty source lines. | 21 | +8.4 |
| Byte entropyHow varied the bytes in the source text are. Repeated bytes give a lower value; a more even mixture gives a higher value. | 4.44 | −6.66 |
Intercept 8.87 + feature contributions = -9.826 (log-odds).
Score = sigmoid(-9.826) = 0.
| Score | 0.945 |
|---|
Feature contributions
| Feature | Value | Contribution (log-odds) |
|---|---|---|
| Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right. | 89 | +0.632 |
| Number layout frequencyHow rapidly the number of numeric values per line changes through the code. | 1 | +0.398 |
| Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *. | 0.061 | +0.35 |
| Indentation frequencyHow rapidly indentation changes from line to line. | 12 | −0.322 |
| Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code. | 21 | +0.293 |
| Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom. | 18.978 | −0.145 |
| 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. | 89 | −0.104 |
Intercept 0.07 + feature contributions = 1.171 (log-odds).
Score = sigmoid(1.171) = 0.763.
| Score | 0.209 |
|---|
| Score | 13 |
|---|
Run 1
The code is very readable due to its clear, linear structure and consistent indentation. It avoids deep nesting entirely, with all statements at the top level of the main method, making the flow easy to follow. The intent is explicitly stated through comments before each tongue twister, and each System.out.println call performs a single, obvious action. While the repeated println calls could be shortened using loops or concatenation, the current approach prioritizes clarity over brevity, which is appropriate for a simple demonstration. The natural reading order——grouped by tongue twister with blank lines between sections——further enhances comprehension. Minor deductions are for slight repetition and the lack of a final closing blank line, but overall it is an excellent example of clear, simple code.
Run 2
The code is highly readable due to its flat, simple structure with no nesting or complex logic. Each action is a single print statement, making the intent clear. Comments logically separate the three tongue twisters, improving navigation. Although repetitive print statements make the code slightly longer than necessary, the format directly mirrors the desired output, which is appropriate for this purpose. The reading flow is natural and follows the sequence of the twisters. Overall, it is clear and well-organized with no ambiguity.
Run 3
The code is highly readable. It has a clear, logical structure with a single class and main method. Nesting is minimal—just one level. The intent is obvious: print three tongue twisters. Comments clearly separate each section. The code length is appropriate; each statement is necessary. Action granularity follows one-action-per-line, with each System.out.println on its own line. Reading flow is natural, progressing through the twisters in order. Minor deductions: repeated print statements could be condensed with loops or text blocks, but this style is acceptable for a simple example. Spacing and indentation are consistent, though four-space indentation would be slightly more conventional than the five spaces used. Overall, it is straightforward, well-commented, and easy to follow.
Run 1
Code Structure: Logically organized into three clearly separated tongue-twister sections. Nesting: Minimal, with only the class and main method scopes. Clarity of intent: The class name, comments, and explicit print statements make the purpose immediately obvious. Code length: Appropriately short; repeated print calls are reasonable for this simple task. Action granularity: Each statement performs one printing action on its own line. Reading flow: Sequential execution, section comments, and blank lines make the output easy to follow. Minor indentation inconsistencies slightly reduce visual polish.
Run 2
Code Structure: Logically organized into three clearly separated tongue-twister blocks. Nesting: Minimal, with only the class and main method. Clarity of intent: The class name, comments, and explicit print statements make the purpose immediately clear. Code length: Appropriately concise for printing fixed text; repetition is straightforward rather than unnecessarily complex. Action granularity: Each line performs a single print action. Reading flow: Output follows a natural top-to-bottom sequence, supported by blank lines and descriptive comments. Slightly inconsistent indentation is the only notable readability weakness.
Run 3
Code Structure: Three clearly separated, commented blocks logically organize the tongue twisters. Nesting: Only the necessary class and method nesting is present. Clarity of intent: The class name, comments, and explicit print statements make the purpose immediately apparent. Code length: Appropriately concise for printing fixed text; repeated println calls are straightforward rather than unnecessarily verbose. Action granularity: Each line performs a single print action. Reading flow: Output follows a natural top-to-bottom sequence, with blank lines separating sections. Slightly inconsistent indentation is the only notable readability weakness.