PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

Customer Stories with DoSomething.org

hackerone.com | blog | #code-review | #customer-story | #engineering | #pullrequest | #developer-productivity | #dosomething
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

DoSomething.org used PullRequest's on-demand code review to scale its small engineering team. Average pull request lifespan dropped to 21 hours, letting the nonprofit ship features faster.
Published
Collected

Related coverage

blog · hackerone.com
The $85 Billion Cost of Bad Code
A Stripe and Harris Poll study found developers spend 42% of their time on technical debt and maintenance, with bad code costing $85 billion annually. Healthy code review processes help address this.
blog · hackerone.com
Customer Stories with Branch
Branch, an insurance startup in five states, uses PullRequest for on-demand code review across its languages and frameworks. CTO Joe Emison values the plug-and-play reviews as the team scales.
blog · hackerone.com
Customer Stories with Silvercar by Audi
Silvercar by Audi, an app-based premium car rental in 25 US cities, scaled code review with PullRequest after its acquisition. VP Jeffrey Kalikstein credits on-demand senior reviewers for its growth.
blog · hackerone.com
Flexible Data Retrieval at Scale with HAQL
HAQL is HackerOne's simplified, strictly typed query interface for building performant aggregate queries on analysis-modeled tables, enabling secure access control and low-code dashboard development.
blog · hackerone.com
Celebrating International Women in Engineering Day
HackerOne marks International Women in Engineering Day, discussing representation and retention challenges for women engineers and sharing internal efforts such as the Women@ employee resource group.
blog · hackerone.com
Precision Matters: Why Using Cents Instead of Floating Point for Transaction Amounts is Crucial
Explains why storing transaction amounts as integer cents is safer than floating-point dollars, covering rounding errors and precision pitfalls in financial code.
Back