‹ BackHN Continuity

Thread

Towards Self-Driving Codebases

123 points · 100 comments · wilhelmklopp

  1. wrs · · focus · HN ↗
    This would be more convincing if there were a simple stat on the home page of the dispositions of the reported bugs (fixed/no-repro/won't-fix).

    As a random sample of one, I looked at one of the bugs this reported on Tailscale (first thing on the homepage) [0], and the pull request ends with "Apologies for the lack of due diligence here. I'll go ahead and close this out."

    [0] <a href="https:&#x2F;&#x2F;github.com&#x2F;tailscale&#x2F;tailscale&#x2F;pull&#x2F;17843" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;tailscale&#x2F;tailscale&#x2F;pull&#x2F;17843

    1. drob · · focus · HN ↗
      We should publish some stats. The fix rates on bugs are around 45% baseline, increasing over time as we learn from behavior within a given codebase. The merge rates for the codebase health work we do (e.g. deleting dead code) are very high, at least 90%.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.