<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>code reviews on Rietta Cybersecurity</title>
    <link>https://rietta.com/tags/code-reviews/</link>
    <description>Recent content in code reviews on Rietta Cybersecurity</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>1999-2026 Rietta Inc. All Rights Reserved.</copyright>
    <atom:link href="https://rietta.com/tags/code-reviews/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Remote Team Culture - Code Review and Style Guides</title>
      <link>https://rietta.com/blog/code-styles-in-small-remote-teams/</link>
      <pubDate>Sat, 12 Dec 2020 02:30:00 -0600</pubDate>
      <guid>https://rietta.com/blog/code-styles-in-small-remote-teams/</guid>
      <description>Code Review at Rietta When joining a new team, a developer can be nervous when making their first pull request or contribution to a codebase.&#xA;The thought of your team going through your code and ripping it to shreds is both reasonable and scary. So how does a team eliminate this fear and instead, encourage newer developers to greet code reviews as a opportunity to not only improve their code, but to encourage a healthier environment to actually collaborate?</description>
    </item>
  </channel>
</rss>
