Remove dead link from docs (#1400)

docs/best-practices/code-reviews/readme.md

@@ -5,7 +5,6 @@
 [XKCD 'Code Quality', copied under CC BY-NC 2.5](https://xkcd.com/1513/)
 
 The Internet provides a wealth of material on code reviews: 
-[on the effect of code review on company culture](https://blog.fullstory.com/what-we-learned-from-google-code-reviews-arent-just-for-catching-bugs/),
 [on formal security reviews](https://www.owasp.org/images/2/2e/OWASP_Code_Review_Guide-V1_1.pdf),
 [shorter guides](https://github.com/thoughtbot/guides/tree/master/code-review),
 [longer checklists](https://www.codeproject.com/Articles/524235/Codeplusreviewplusguidelines),
@@ -34,8 +33,7 @@ This guide covers the following topics:
 ## Motivation
 
 We perform code reviews (CRs) in order to improve code quality and benefit from
-[positive effects on team and company
-culture](https://blog.fullstory.com/what-we-learned-from-google-code-reviews-arent-just-for-catching-bugs/).
+positive effects on team and company culture.
 For example:
 
 - **Committers are motivated** by the notion of a set
@@ -50,7 +48,7 @@ For example:
     team members who can subsequently build on the work done.
 
   - The committer may use a technique or algorithm that reviewers can
-    learn from. More generally, code reviews help [raise the quality bar across the organization](https://blog.fullstory.com/what-we-learned-from-google-code-reviews-arent-just-for-catching-bugs/).
+    learn from. More generally, code reviews help raise the quality bar across the organization.
 
   - Reviewers may possess knowledge about programming techniques or the code base that can help
     improve or consolidate the change; for example, someone else may be