Sample

Buse/44

Human rating uses the original dataset scale.

DatasetBuse
Human4.07
Lines5

Scores

MethodScoreScaleDataset rank
(0–100)
Posnett0.9250–1; higher is more readable
87.9Δ 4.5
Scalabrino0.8640–1; higher is more readable
81.8Δ 10.6
Dorn0.7950–1; higher is more readable
81.8Δ 10.6
Mi0.6670–1; higher is more readable
71.7Δ 20.7
LLOC4Logical lines; fewer is more readable
59.6Δ 32.8
DeepSeek V4 Pro10.670–20; mean of three runs
20.7Δ 71.7
GPT-6.1 Sol15.330–20; mean of three runs
39.9Δ 52.5
BTTF0.6030–1; higher is more readable
74.7Δ 17.7
Human4.071–5; original rating
92.4

Views

Download official ZIP ↗

Select the downloaded ZIP or its extracted folder. Files stay in your browser.

Loading feature diagnosis…

Source regions

Feature contributions

Feature contributions

FeatureValueContribution
(log-odds)
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.539−5.309
Halstead volumeHow much symbolic information the code contains. It combines the total number of operators and values with the number of distinct ones.92.511−3.053
Source linesThe number of non-empty source lines.5+2

Intercept 8.87 + feature contributions = 2.508 (log-odds).
Score = sigmoid(2.508) = 0.925.

Score0.864

Feature contributions

FeatureValueContribution
(log-odds)
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.43+1.844
Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code.6+0.824
Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right.0−0.804
Indentation frequencyHow rapidly indentation changes from line to line.1−0.703
Number layout frequencyHow rapidly the number of numeric values per line changes through the code.1+0.398
Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom.4.636−0.345
Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *.0.09+0.072

Intercept 0.07 + feature contributions = 1.356 (log-odds).
Score = sigmoid(1.356) = 0.795.

Score0.667
Score4
Run 1

The code snippet is minimal, which helps with concise length and action granularity, but it severely lacks clarity and context. The method name 'link' is vague, and the variable names 'other', 'next', and 'last' are ambiguous without surrounding class definitions or documentation. The line 'other.last = this;' appears to be a typo—likely should be 'other.last = last;'—further confusing intent. The structure is flat, which is good, but the logical organization and reading flow suffer due to unexplained relationships between objects. Without comments or clear naming, a reader cannot easily infer the purpose of this linking operation. Overall, it is readable only at a superficial syntactic level, not in terms of understanding functionality.

Run 2

The code is relatively concise and each line performs a single action, which supports action granularity and length. However, readability suffers from unclear intent and missing context: variable names like 'next', 'last', and 'other' are ambiguous without surrounding class definitions. The method 'link' lacks documentation or comments explaining the linking logic. Nesting is flat, which is good, but the overall structure feels incomplete—there is no closing brace shown, and the method's purpose is not self-evident. Reading flow is somewhat natural, but the lack of context and missing terminal brace reduce clarity.

Run 3

The code is fairly readable but lacks context and complete logic. It has a flat structure, one action per line, and clear variable names, which aids readability. However, the method name 'link' is somewhat ambiguous without surrounding context, and the final assignment appears incomplete (likely missing 'next = other;'), hurting clarity of intent. Code length is concise, and nesting is minimal. Overall, readable but not self-contained.

Run 1

Code Structure: The pointer assignments are logically grouped, but the snippet is incomplete, with no closing brace. Nesting: Flat and easy to scan. Clarity of intent: The method name and assignments suggest inserting another iterator into a linked structure, but 'last' is ambiguous and the expected 'next = other' update is not shown, making the resulting linkage unclear. Code length: Concise, with no unnecessary logic. Action granularity: Each line performs one assignment. Reading flow: The sequence is mostly natural, though the extra blank line and inconsistent spacing slightly reduce polish.

Run 2

Code Structure: The three assignments form a logically organized sequence for inserting an iterator into a linked structure, though the snippet is incomplete and lacks a closing brace. Nesting: The method is flat with no nested control flow. Clarity of intent: The link method and pointer assignments suggest insertion, but last is less conventional than prev, and the expected state of next is implicit. Code length: Very concise, with no unnecessary statements. Action granularity: Each line performs one assignment. Reading flow: The assignments are easy to follow in order, although the missing update to this.next leaves the apparent insertion operation incomplete and makes its intended behavior less clear.

Run 3

Code Structure: logically ordered pointer updates, but the snippet is incomplete and lacks a closing brace. Nesting: flat, with no nested control flow. Clarity of intent: link suggests inserting another iterator into a linked structure, though next and last require contextual knowledge. Code length: concise, with no unnecessary statements. Action granularity: each line performs one assignment. Reading flow: the updates follow a natural insertion sequence; minor spacing inconsistency does not significantly hinder readability.