[signal] DORA Metrics Losing Explanatory Power in the AI Era - New Measurement Vocabulary Emerging

[gkanitz]

DORA Metrics Losing Explanatory Power in the AI Era - New Measurement Vocabulary Emerging

Recommended action

Add a section to the CodeRepute transparency manifest and narrative front page explicitly positioning the tool's collaboration-quality signals as complementary to DORA - framing review depth and PR cadence as metrics that remain meaningful even as AI accelerates code output.

Type: positioning

Source

• https://larridin.com/developer-productivity-hub/why-dora-metrics-break-ai-era
• https://uplevelteam.com/blog/why-dora-metrics-are-only-part-of-the-equation
• https://getdx.com/blog/dora-metrics

What people are saying

By 2025, it had changed fundamentally. And by 2026, teams relying solely on DORA metrics are measuring the wrong things.

The 2025 DORA report's central finding is that AI amplifies what's already there.

Why did our change failure rate rise after we adopted AI coding tools? This matches DORA's 2025 findings: increased AI adoption correlates with increased software delivery instability, even as it improves individual effectiveness and code quality.

Why this fits CodeRepute

CodeRepute currently surfaces PR-level collaboration metrics. As DORA metrics lose interpretive power in AI-assisted development, there is a growing need for alternative signals of engineering quality. CodeRepute's focus on review depth, PR-size normalisation, and collaboration cadence is well-positioned as a complement or successor framing. This also creates a content and positioning angle for both vehicles.

Confidence

Origin

Found by Scout (routed from org-wide scan: CodeRepute's PR-level metrics (review depth, PR-size normalisation, collaboration cadence) are directly affected by DORA metrics losing interpretive power, positioning the tool as an alternative measurement framework for engineering quality in AI-assisted development contexts.)

[gkanitz]

Additional signal found

Engineering Intelligence Platforms (LinearB, Jellyfish, Swarmia) Expanding Into AI Adoption Measurement

Swarmia is an engineering intelligence platform that gives engineering leaders one place to see how their teams work, how they feel, and where the investment goes — plus the tools to act on what they find. It brings together engineering metrics (including DORA and SPACE), AI adoption, usage, and cost across every coding tool

Jellyfish is the intelligence platform for AI-Integrated engineering, helping more than 1,000 companies leverage AI to transform how they build software.

Type: competitive

Recommended action: Add a comparison note in the CodeRepute README or landing page that explicitly contrasts the no-org-access, individual-developer model against enterprise intelligence platforms, targeting developers who want portable attestation without granting tool access to their employer's codebase.

Reasoning: Commercial engineering intelligence platforms are expanding into exactly the AI productivity and collaboration measurement space adjacent to CodeRepute. These platforms require deep code and organisation data access - the opposite of CodeRepute's no-source-code, privacy-preserving model. This competitive dynamic validates CodeRepute's privacy angle as a differentiator, particularly for individual developers and small teams who cannot or will not grant full org access.

Confidence: medium

Sources:

• https://www.gartner.com/reviews/market/developer-productivity-insight-platforms
• https://linearb.io/blog/developer-productivity-tools

[gkanitz]

Additional signal found

GitHub contribution graphs are actively gamed, undermining hiring signal credibility

That green grid has become a proxy for developer competence in hiring. Recruiters glance at it. Hiring managers judge it. And thousands of developers have decided to do something about it. They're not learning to code more. They're not contributing to open source. They're running Python scripts that backdate commits to make their profiles look "active."

Type: positioning

Recommended action: Add a section to the transparency manifest and narrative front page explaining specifically why PR-based collaboration metrics are more resistant to backdating and scripted inflation than commit-graph metrics, and use this as a primary positioning statement in outward-facing copy.

Reasoning: CodeRepute's focus on collaboration metadata (PRs authored, reviews given, time to merge) rather than raw commit counts or contribution graphs directly addresses the gaming problem described here. This is a positioning opportunity: CodeRepute can differentiate by explaining why collaboration-activity attestation is harder to game than commit frequency.

Confidence: high

Sources:

• https://medium.com/data-science-collective/developers-are-gaming-their-github-profiles-3f58f1f00c2a

[gkanitz]

Additional signal found

Hacker News discussion surfaces demand for quality-over-quantity GitHub metrics and rejection of composite scores

It's time to foreground quality not just quantity. The GitHub '4 kpis' are entirely action oriented.

The rate of PRs to repos they don't own
The reject rate of PRs
The number of ban
An estimated 'AI' or bot score or status flag

Type: product

Recommended action: Surface the 'no composite score' design decision prominently in the narrative front page and README, citing this community demand as validation. Consider adding a 'merge acceptance rate' metric to the v0.2 roadmap as a low-lift addition to the existing collaboration metadata pull.

Reasoning: HN commenters are explicitly asking for PR-quality signals over raw activity counts, which aligns with CodeRepute's review-comment depth, time-to-merge, and PR-size normalization metrics. The rejection of composite scores echoes CodeRepute's explicit design choice to omit any single ranking or grade.

Confidence: high

Sources:

• https://news.ycombinator.com/item?id=48181125

[gkanitz]

Additional signal found

Devthropology Show HN reveals a direct competitor using banded tiers and color-coded PR metrics for contributor reports

Author/Reviewer reports: A handful of metrics showing performance of a contributor from both sides of a PR, one as an author and one as a reviewer. Cells are color coded and bucketed into tiers to easily see where someone sits in the repository.

Trends/Reports can be filtered by team but unfortunately without a private API key, I cannot sync teams.

Type: competitive

Recommended action: Draft a competitive positioning brief that explicitly contrasts CodeRepute (developer-owned, cross-repo, no within-team comparison, cryptographically attested) against repo-centric tools like Devthropology. Use this framing in landing page copy and the narrative front page.

Reasoning: Devthropology is a near-direct competitor covering the same PR authorship and review metrics with banded tiers. However, it is repo-centric (requires access to a specific repo), compares contributors within a team, and has no cryptographic attestation or privacy guarantees. CodeRepute's developer-centric, privacy-preserving, independently verifiable output is a meaningful differentiator.

Confidence: high

Sources:

• https://news.ycombinator.com/item?id=48848819

[gkanitz]

Additional signal found

HN developer productivity metric discussion warns that context-free scores mislead managers and are widely misused

You will be surprised by how many times people want a simple score or a simple graph to summarize how productive a developer is. What really bugs me about lines of code/number of commits/etc. metrics is they are actually really useful for developers, but because they are used incorrectly, it takes a lot of effort to explain to people that context matters.

Type: product

Recommended action: Use the interpretive banded ranges and narrative front page copy to explicitly explain what each metric does and does not indicate, with a short 'how to read this report' section that pre-empts manager misuse. Phrase it as a feature of the transparency manifest.

Reasoning: This directly validates CodeRepute v0.2's 'Meaning' wave rationale: adding banded ranges, PR-size normalization, and interpretive narrative context to raw metrics. The community pain point is that raw numbers get misread without context, which is exactly what the current wave is designed to address.

Confidence: high

Sources:

• https://news.ycombinator.com/item?id=26980731

[gkanitz]

Additional signal found

Portability of developer reputation across platforms is an emerging but unresolved need

A developer could carry proof of contributions across different platforms without rebuilding their reputation each time. This aligns with a broader trend in Web3 where identity and reputation are not tied to a single application. But portability introduces its own challenges.

It depends on whether issuers can establish credibility.

Type: architecture

Recommended action: Publish a clear specification of the attestation format and verification steps in the transparency manifest so that third parties can independently verify a report without trusting CodeRepute as an intermediary. Spike a CLI verification command that any party can run against a published report hash.

Reasoning: CodeRepute's cryptographically attested, independently verifiable reports are a direct answer to the portability problem described here. The question of issuer credibility is a risk CodeRepute must address to gain adoption among hiring managers and independent verifiers.

Confidence: medium

Sources:

• https://www.binance.com/en/square/post/306028033463617

[gkanitz]

Additional signal found

4.5 million fake GitHub stars signal broad metric manipulation, with community consensus that automated reputation scoring is fundamentally flawed

build, I've come to the firm conclusion that these metrics are just plain bad if one uses them as a basis to make any significant decision.

You can't automate reputation scoring.

Type: positioning

Recommended action: Ensure all product copy, the README, and the narrative front page lead with what CodeRepute is not: not a score, not a ranking, not a judge of quality. Frame it as a cryptographic receipt of observable activity, and use the transparency manifest to let skeptics audit every data point that was read.

Reasoning: Skepticism about any automated developer reputation metric is strong in the HN community. CodeRepute's explicit design choices (no composite score, no ranking, transparency manifest) are the correct mitigation, but this sentiment represents an adoption risk if the product is perceived as another scoring system.

Confidence: medium

Sources:

• https://news.ycombinator.com/item?id=42540182

[gkanitz]

Additional signal found

Graphite and LinearB dominate the PR analytics space for engineering managers, framing metrics as productivity and DORA tools

In this situation, you can shorten the time to review code by looking at the metric that shows how many individual PRs each engineer merges.

LinearB leads PR analytics and DORA metrics.

Swarmia focuses on the SPACE framework and developer experience surveys alongside DORA metrics.

Type: competitive

Recommended action: Position CodeRepute explicitly as a developer-owned credential tool rather than a manager analytics tool. Avoid feature overlap language like 'DORA metrics' or 'cycle time' in copy. Emphasize that the report belongs to the developer, not the employer.

Reasoning: The PR analytics market is occupied by team-productivity tools (LinearB, Swarmia, Haystack, Graphite) aimed at engineering managers. CodeRepute's developer-centric, privacy-preserving, portable attestation for individual developers is a distinct and unoccupied niche. None of these tools produce independently verifiable, developer-owned reports.

Confidence: high

Sources:

• https://graphite.com/guides/github-pr-metrics
• https://codeant.ai/blogs/top-pull-request-automation-tools

[gkanitz]

Additional signal found

Open Badges 3.0 aligned with VCDM creating an emerging hiring-pipeline credential ecosystem

Open Badges 3.0 is the international standard for verifiable digital credentials, maintained by the 1EdTech Consortium and aligned with the W3C Verifiable Credentials Data Model. It enables institutions to issue tamper-proof, cryptographically signed credentials that anyone can verify independently.

From a trust perspective, Open Badges 3.0 leans on VC conventions: verifiers can validate cryptographic proofs and read standardised metadata instead of relying on screenshots or manual paperwork.

Type: product

Recommended action: Investigate whether CodeRepute's transparency manifest and share card can be issued as an Open Badges 3.0 credential, enabling direct import into HR platforms and digital wallets - add to the v0.3 roadmap as a candidate feature.

Reasoning: CodeRepute's core value is independent verifiability of developer activity. Open Badges 3.0 is being adopted by the hiring pipeline (HR tech, ATS vendors) that CodeRepute reports are designed to feed into. Alignment with this standard would make CodeRepute reports natively portable into those pipelines without custom integrations.

Confidence: medium

Sources:

• https://www.pok.tech/en/digital-credentials/open-badge-3-0
• https://certopus.com/blog/open-badges-3