How "Penis-Pull-Requesting" affects Teams & Products
summary
Claims that ego-driven pull requests — coined Penis-Pull-Requesting — regularly stall shipping: a simple "show the magic price" feature (backend and CMS already done) sits ready Monday but becomes a week-long delay after a junior vs senior debate about iterating with forEach vs map and alleged performance. The feature finally merges Friday but waits for Monday deployment. Observed frequency: 3 PPRs per team per month. Remedies include surfacing the why, adding role/type checks, enforced processes, retros, pairing and agile coach escalation.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:02What Is a Pull Request
- 17:56Solutions
- 27:02Questions
- 29:53The Conflict between Junior and Senior Developers
- 30:05What Are Solutions for Interpersonal Fights between Rockstar Developers and Junior Developers
- 33:33Theory of Broken Windows
related talks
39mHow Pull Requests Steal Your Time
23mThe Art of the Pull Request
16mAn unpopular opinion: Get rid of Pull Requests!
11mPull Requests: Merge With Your Team
28mPull Requests: Merging good practices into your project
29mThe Art of Humanizing Pull Requests (PR’s)
26mA State of Continuous Merge: The Secret to More Productive Dev Teams
38mPull Requests and Reviews for Good