Akash Kumar

66 of 100, ranked 10 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 66. That difference is carried by infrastructure (18 against a cohort median of 50, worth -6.2 points) and consistency (45 against a cohort median of 53, worth -1.2 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 66 − 73 = -7, 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: 488.1 hours tracked, 100 commits, 1,064,329 lines changed, 16.6% 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.

• ⚑ This score describes 53% of their recorded working time

  Rule: fires below 70% coverage with at least 20 tracked days — 32 of 60 days produced a commit, review, task or infrastructure change.

  What it does not mean: The other 28 days were worked and tracked, and produced nothing any connected system records. That is meetings, support, debugging, planning and infrastructure without an AWS account mapped — work this platform is blind to, not work that did not happen. It does not lower the score; it bounds what the score is about.

• ⚑ 1,064,329 lines changed in this window

  Rule: fires above 500,000 lines added + deleted — measured 1,064,329.

  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

• route53 ChangeResourceRecordSets×14 · 28 pts
• ses CreateEmailIdentity×4 · 20 pts
• amplify StartJob×4 · 16 pts
• amplify UpdateApp×2 · 8 pts
• ses PutEmailIdentityDkimAttributes×4 · 8 pts
• ec2 AuthorizeSecurityGroupIngress×2 · 6 pts
• q SendMessage×3 · 6 pts
• ec2 RunInstances×1 · 5 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.