{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Code Review Culture: Why You Need to Have One","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/bcf8f2d9\"></iframe>","width":"100%","height":180,"duration":789,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/code-review-culture-why-you-need-to-have-one.\nCode review culture is important to avoid friction in your team and bugs in code. As reviewers, you want to avoid personal style comments (aka nitpicks)\nCheck more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #code-review, #code-review-best-practices, #reviewing-pull-requests, #swift, #engineering-culture, #code-review-guide, #coding-culture, #coding-review-tips,  and more.\nThis story was written by: @jemsberliner. Learn more about this writer by checking @jemsberliner's about page,\n            and for more stories, please visit hackernoon.com.\nCode review culture is important to avoid friction in your team and bugs in code. As reviewers, you want to avoid personal style comments (aka nitpicks) and focus on the essentials. As a team, it is recommended to agree on a set of guidelines on how to communicate in pull requests and what to focus on first.","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}