<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Satire on PullRequest</title><link>https://www.pullrequest.com/categories/satire/</link><description>Recent content in Satire on PullRequest</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 17 Aug 2018 08:45:24 -0500</lastBuildDate><atom:link href="https://www.pullrequest.com/categories/satire/index.xml" rel="self" type="application/rss+xml"/><item><title>Seven Habits for a More Toxic Code Review Culture</title><link>https://www.pullrequest.com/blog/7-habits-for-more-toxic-code-review/</link><pubDate>Fri, 17 Aug 2018 08:45:24 -0500</pubDate><guid>https://www.pullrequest.com/blog/7-habits-for-more-toxic-code-review/</guid><description>&lt;p>&lt;em>Please don&amp;rsquo;t practice any of the following &amp;ldquo;advice.&amp;rdquo; From junior developer to CTO of a Fortune 500, we&amp;rsquo;re all guilty of making mistakes within development. We&amp;rsquo;ve picked the worst examples we&amp;rsquo;ve seen around code review and pulled them together into one terrible, awful reviewer:&lt;/em>&lt;/p>
&lt;p>Look — I get it. You&amp;rsquo;ve done everything you could to ensure that no one would ever ask you to do a code review, but they&amp;rsquo;ve gone and promoted you anyhow. Now you have a whole team to bring down with you, down to the depths of a toxic code review culture.&lt;/p>
&lt;p>This won&amp;rsquo;t be easy — making enemies never is — but if you follow these seven highly effective habits, no one on your team will even think about submitting a pull request. And less pushes means less work. Win-win.&lt;/p></description></item></channel></rss>