Reviewing One's Own Code
hackerone.com | blog | #code-review | #best-practices | #pull-request | #engineering-culture | #developer-practices | #self-review | #cognitive-bias | #developer-tips
Summary
Before opening a pull request, developers should review their own code: shifting context, changing diff views, and pausing creates the cognitive distance to catch issues early.
- Published
- Collected
--- id: 2796 title: "Reviewing One's Own Code" source_domain: hackerone.com source_url: "https://www.hackerone.com/blog/reviewing-ones-own-code" published_at: "2021-12-13T00:00:00Z" tags: ["code-review", "best-practices", "pull-request", "engineering-culture", "developer-practices", "self-review", "cognitive-bias", "developer-tips"] phying_url: "https://phying.com/item/2796" lang: en --- # Reviewing One's Own Code ## Summary Before opening a pull request, developers should review their own code: shifting context, changing diff views, and pausing creates the cognitive distance to catch issues early. ## Intelligence Metadata - **Sources:** hackerone.com - **Published:** 2021-12-13T00:00:00Z - **Original:** https://www.hackerone.com/blog/reviewing-ones-own-code - **Phying News:** https://phying.com/item/2796