Harsh Patel

71 of 100, ranked 8 of 14 people with a score, against a cohort median of 71. The bands are cut from this period's own distribution, not fixed thresholds: ≤ 66 is behind, ≥ 73 is leading, and this person is in the middle 40% of people with a score this period. With every component at the cohort median this person would score 73; they score 71. That difference is carried by craft (58 against a cohort median of 97, worth -12.5 points). 1 of 6 components (completed work) could not be measured at all, so the remaining weights were rescaled — this score rests on 78% of the intended evidence.

A band compares this person to the 14 people who have a score in this window — nothing more. It is not a rating, it does not persist, and it moves when the cohort or the window moves.

Effect is a counterfactual, not a share: how many points this person’s score would move if that one component dropped to the cohort median for it. The effects sum to 71 − 73 = -2, where 73 is what this person would score with every one of their components at the cohort median. Negative rows are the reason the total sits where it does. A component with no data is withheld and the remaining weights are rescaled — it is never scored as zero, and it never counts against anyone.

Measured but deliberately not scored: 526.0 hours tracked, 195 commits, 564,768 lines changed, 10.1% activity. The first four measure motion rather than delivery and are trivially inflated. CI is excluded because it exists on a minority of repositories, so scoring it would rank people by which repository they work in. This score cannot see architecture, planning, mentoring, incident response or infrastructure work at all.

• ⚑ 564,768 lines changed in this window

  Rule: fires above 500,000 lines added + deleted — measured 564,768.

  What it does not mean: Churn is never scored, precisely because it is this easy to inflate. The flag exists to stop a large number being read as a large contribution. Check for a vendored directory or a bulk import.

What they actually did

• ec2 DeleteSecurityGroup×135 · 405 pts
• autoscaling SuspendProcesses×172 · 344 pts
• elasticbeanstalk UpdateEnvironment×83 · 332 pts
• cloudformation UpdateStack×75 · 300 pts
• autoscaling UpdateAutoScalingGroup×128 · 256 pts
• autoscaling TerminateInstanceInAutoScalingGroup×49 · 245 pts
• route53 ChangeResourceRecordSets×119 · 238 pts
• ec2 AuthorizeSecurityGroupIngress×66 · 198 pts

CloudTrail records the API call, not the intent. It cannot tell a considered change from one corrected a minute later, and it retains 90 days — so an empty earlier period means “not retained”, never “nothing happened”.

No pull requests opened or merged by this person in this window.