Weave
Dev tools
engineering metrics
SHOW HN2024
How HN took it
0 positive, 3 neutral or asking, 0 mixed, 16 critical, out of 19 comments about the project. Thread score -0.56.
Idea: 0 for, 10 againstDocs: 0 for, 3 againstPerformance: 0 for, 2 againstExecution: 0 for, 1 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Maker says startup testers gave fantastic feedback
From 1 comment
Objections
Metric can be gamed once known
From 1 comment
As soon as people know how the metric is calculated, they will game that metric and it will cease to be useful.
henning on HN
Ignores maintenance, bug fixes and outcome or product impact
From 3 comments
In a complex, mature system, a high impact bug could have a very small fix that is highly non-obvious. Your metric assumes that the person shitting out 1000 lines of a new…
henning on HNA hotfix PR that was 2 lines long, prevents (or managed) an outage incident, but was merged with no title, description, or review because time was of the essence. Some of such…
captn3m0 on HNIf you build something that doesn't solve problems with impact to the business, your real productivity is zero. How does this account for that?…
jaredsohn on HN
Black-box metric with little information on the landing page
From 2 comments
I'd like to add that you need way more information on the landing page before I'm going to do much more than let you have my email address (if that.) Right now its a black box…
karmajunkie on HNI worked as a manager in a big tech company that used metrics such as amount of PRs done, amount of PR reviews and etc. At least with those when there were questions based on…
id00 on HN
Effort cannot be inferred from code alone; context switching ignored
From 2 comments
Pretty dumb to think you can infer effort from the code itself. You make one "smart invocation" to a remote microservice and replace 1000 lines of code! The information for…
mg57 on HNCurious how these numbers correlate to the estimates of the engineers behind the PRs? For example, the first PR is correlated with ~15 "hours of work for an expert engineer"…
jumploops on HN
Requests
More detail on how the correlation numbers were validated
From 2 comments
How did you come up with those magic correlation numbers? Is this generally just sniffing surface quality and quantity of written code, or is consideration given to how…
rkagerer on HNHey HN! I'm one of the co-founders of Weave, and I wanted to jump in here to share a bit more. Building this has been a wild ride. The challenge of measuring engineering output…
adambeecee on HN
Explain how the metric handles refactoring and long-term regressions
From 1 comment
Let me just ignore my natural distain to the whole thing (as a engineer and a manager) > We’ve developed a custom model that analyzes code and its impact directly... This is a…
id00 on HN
Questions
How were the 0.94 and 0.3/0.35 correlation figures computed
From 2 comments
How did you come up with those magic correlation numbers? Is this generally just sniffing surface quality and quantity of written code, or is consideration given to how…
rkagerer on HN> How did you come up with those magic correlation numbers? Evaluated on a proprietary data set of manually labelled PRs > Is this generally just sniffing surface quality and…
adchurch on HN
Does it account for branches that never reach production
From 1 comment
Skeptic here. How can you validate the difference in effort from a startup where growth happens in explosive moments with many rewrites in between vs a refined enterprise…
cssanchez on HN
Alternatives named
Lines of code, PR counts and story points
From 1 comment