<?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 CTOMultiplier</title><link>https://ctomultiplier.com/tags/code-reviews/</link><description>Recent content in Code Reviews on CTOMultiplier</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 25 Sep 2025 22:12:26 +0200</lastBuildDate><atom:link href="https://ctomultiplier.com/tags/code-reviews/feed.xml" rel="self" type="application/rss+xml"/><item><title>Guide to do Code Reviews in your team</title><link>https://ctomultiplier.com/guide-to-do-code-reviews-in-your-team/</link><pubDate>Tue, 25 Jul 2023 15:42:32 +0000</pubDate><guid>https://ctomultiplier.com/guide-to-do-code-reviews-in-your-team/</guid><description>&lt;p&gt;Code reviews are a practice that has become widespread in recent years, where one or more developers review the new code implemented by another colleague, with the aim of detecting code quality issues, bugs, vulnerabilities, bad practices, etc&amp;hellip; . This allows feedback loops to be shortened, which we know is very beneficial because the later a problem is discovered, the higher the cost of fixing it and the greater the potential business impact.&lt;/p&gt;</description></item></channel></rss>