Sample

Buse/14

Human rating uses the original dataset scale.

DatasetBuse
Human4.05
Lines11

Scores

MethodScoreScaleDataset rank
(0–100)
Posnett0.6860–1; higher is more readable
72.7Δ 17.7
Scalabrino0.8280–1; higher is more readable
65.2Δ 25.3
Dorn0.8860–1; higher is more readable
99.0Δ 8.6
Mi0.660–1; higher is more readable
69.7Δ 20.7
LLOC5Logical lines; fewer is more readable
29.8Δ 60.6
DeepSeek V4 Pro16.330–20; mean of three runs
77.3Δ 13.1
GPT-6.1 Sol17.330–20; mean of three runs
71.7Δ 18.7
BTTF0.5770–1; higher is more readable
65.7Δ 24.7
Human4.051–5; original rating
90.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.4.291−6.436
Halstead volumeHow much symbolic information the code contains. It combines the total number of operators and values with the number of distinct ones.183.399−6.052
Source linesThe number of non-empty source lines.11+4.4

Intercept 8.87 + feature contributions = 0.781 (log-odds).
Score = sigmoid(0.781) = 0.686.

Score0.828

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.57+1.251
Comment layout frequencyHow frequently the layout switches between lines containing only comments or whitespace and lines containing code.9+0.718
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.10−0.391
Identifier layout (vertical)How rapidly the visual pattern of identifier characters changes from top to bottom.10.776−0.259
Operator visual areaThe share of the code’s visual area occupied by operators such as +, =, and *.0.081+0.152
Comment layout (horizontal)How rapidly the visual pattern of comment characters changes from left to right.57+0.115

Intercept 0.07 + feature contributions = 2.053 (log-odds).
Score = sigmoid(2.053) = 0.886.

Score0.66
Score5
Run 1

The code is well-structured, flat, and concise. It performs one clear action: removing a name from a list and handling the null case. Nesting is minimal with a single conditional block. The intent is obvious and the exception is appropriately thrown. Slight points deducted for the generic exception type and the possibly redundant comment.

Run 2

The code is well-structured and highly readable. It has a clear single responsibility: remove a name from a list and handle the null case. Nesting is minimal with only one conditional block. The intent is unambiguous — if the name isn't found, throw a traceable error; otherwise return the removed owner. Code length is appropriately concise, and each line performs a distinct action. The reading flow is natural from operation to validation to return. Minor deductions: the comment 'should contain name' could be clearer about why the name is expected to exist, and the exception type is generic, which slightly obscures the specific failure condition.

Run 3

The code is clear and well-structured. It performs a single operation (removing a name from a list) with a null check and an explicit exception. Structure is logical: fetch, validate, return. Nesting is minimal (one if block). Intent is obvious: remove an entry and error if absent. Length is concise, with no redundancy. Action granularity is good — each step is on its own line. Reading flow is natural: top-to-bottom, straightforward. Minor deductions: the comment '// should contain name' is slightly vague and could be more explicit about the invariant violation, and the exception uses a generic error code rather than a specific one. Overall, the method is highly readable and maintainable.

Run 1

Code Structure: logically organized into removal, validation, and return, though the snippet lacks a closing method brace. Nesting: a single shallow conditional is easy to follow. Clarity of intent: the method and variable names convey removing a name and returning its owner; the generic error and vague comment provide little context when removal fails. Code length: concise, with slightly excessive blank lines. Action granularity: each statement performs one clear action. Reading flow: natural and sequential, with failure handled before the successful return.

Run 2

Code Structure: The method follows a logical remove-check-return sequence, but the missing closing brace leaves the snippet incomplete. Nesting: A single shallow conditional is easy to follow. Clarity of intent: The method name and removal operation clearly convey its purpose; however, the generic Object type, vague comment, and GENERAL_ERROR provide limited context. Code length: The implementation is concise, though excessive blank lines interrupt its compactness. Action granularity: Each statement performs one action. Reading flow: Execution proceeds naturally from removal to validation and return, with only the whitespace and incomplete method boundary detracting from readability.

Run 3

Code Structure: logically organized into removal, validation, and return, though the method's closing brace is missing. Nesting: shallow, with only one conditional. Clarity of intent: the method and variable names communicate removal and returning the associated owner; however, the generic error and vague comment provide little context. Code length: concise, although excessive blank lines interrupt the compact method. Action granularity: each statement performs one clear action. Reading flow: straightforward and sequential, with the missing brace slightly undermining completeness.