mgreene

7 ms·

1.
by mgreene 2y ago
For the lowest risk changes in terms of review comment activity, that appears to almost already be happening.
2.
by mgreene 2y ago
Not an unreasonable thing to say. I did provide data to back up my point of view so folks are at least free to disagree on the details rather than just the high-level take.
3.
by mgreene 2y ago
Building upon Microsoft's earlier analysis ( https://pdfs.semanticscholar.org/c079/0dc547c56ca48b78bc418b... ), our data, which is composed through an objective risk measure, confirms similar findings about code rev
4.
Code Reviews Are Not Effective at Finding Bugs(shepherdly.io)
2 points by mgreene 2y ago|7 comments
5.
by mgreene 2y ago
The paper's title is a bit provocative but I think the findings are interesting. Mainly around long-held beliefs about what developers perceive as the value vs what is actually happening. You do bring up a good point about using change
6.
Benchmarking Risk and Quality KPIs in Popular Open Source Projects(shepherdly.io)
1 points by mgreene 3y ago|1 comments
7.
by mgreene 3y ago
Shepherdly is a bug prediction platform for pull requests. We wanted to see how risky PRs were managed in open source repositories. How do you think it compares to yours?
8.
by mgreene 6y ago
WHOOP | Backend, Full stack, iOS Engineers | Boston | Full-time | ONSITE (Remote for COVID) WHOOP is a fitness tracker that has the goal of optimizing performance for everybody from professional athletes to everyday people hoping to stay a
9.
Newbie's guide to Apache Spark tuning(evertrue.github.io)
1 points by mgreene 11y ago|0 comments
10.
by mgreene 12y ago
How much of the c3.xlarge memory should be reserved for file system caching?