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

Slaying Dragon Code Reviews

hackerone.com | blog | #code-review | #best-practices | #pull-request | #software-engineering | #development-workflow
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

Adam Beaton offers tactics for taming oversized 'dragon' code reviews - changesets touching thousands of lines and multiple responsibilities - so they can still be reviewed effectively.
Published
Collected

Related coverage

blog · hackerone.com
The Benefits of Code Review From an Outside Perspective
An engineer who moved from a Fortune-scale company to PullRequest explains how disciplined code review works, why large teams skip it, and the quality gains from outside reviewers.
blog · hackerone.com
11 Ways to Create Pull Requests that are Easy to Review
Eleven habits for review-friendly pull requests: keep them under 500 lines, enforce consistent style with linters, write self-documenting code, unit tests, and intent comments.
blog · borghq.io
How Automatic Retests Verify a Fix When Your PR Merges
How Borg's Odin verifies fixes when a linked pull request merges: it reviews the merged code change rather than the running app, deciding whether a finding is resolved, plus its limits.
blog · hacktron.ai
Introducing Hacktron Review
Hacktron Review is an AI security reviewer for pull requests that understands codebase context, reduces false positives, and catches exploitable vulnerabilities before they are merged.
blog · hackerone.com
How HackerOne Reinvented Security for Developers
HackerOne's Code Security pairs SAST, SCA, IaC and secrets scanning with an AI Context Engine, surfacing human-validated findings in pull requests while Hai Hotspots probes architectural risks.
blog · hackerone.com
How to Effectively Split Large Changes into Smaller, Reviewable Pieces
Reviewing large pull requests is slow and error-prone. This guide shows how to break work into independent logical units, using an authentication feature as the example.
Back