<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code-Review on Mohammad Jashem — Senior Full-Stack Mobile Engineer</title><link>https://mjashem.com/tags/code-review/</link><description>Recent content in Code-Review on Mohammad Jashem — Senior Full-Stack Mobile Engineer</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>mjashem@hotmail.com (Mohammad Jashem)</managingEditor><webMaster>mjashem@hotmail.com (Mohammad Jashem)</webMaster><lastBuildDate>Wed, 08 Jul 2026 00:00:00 +0600</lastBuildDate><atom:link href="https://mjashem.com/tags/code-review/index.xml" rel="self" type="application/rss+xml"/><item><title>AI Code Review in CI/CD: From Slow Reviews to Instant</title><link>https://mjashem.com/insights/ai-code-review-in-ci-cd/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0600</pubDate><author>mjashem@hotmail.com (Mohammad Jashem)</author><guid>https://mjashem.com/insights/ai-code-review-in-ci-cd/</guid><description>&lt;p&gt;Review latency is the quietest killer of release cadence on a long-running app. The build ships in minutes, the pipeline promotes in minutes, and then a PR sits for a day and a half waiting for a human to look at it. I&amp;rsquo;m a senior mobile architect — I&amp;rsquo;ve maintained the &lt;a
href="https://mjashem.com/projects/ncc-mobile-app/"&gt;NCC App&lt;/a&gt; for seven-plus years across three stores — and for a long stretch the bottleneck on my own pipeline was me. Adding AI code review to CI/CD is the single change that collapsed that latency. This is the write-up on how it&amp;rsquo;s wired, what it catches, what it misses, and why a human still signs off on every merge.&lt;/p&gt;</description></item></channel></rss>