<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Blog - R5 | AI Strategy, Engineering, and Fractional CTO Consulting</title><link>https://rfive.ai/blog/</link><description>Short articles on AI strategy, architecture, and machine learning engineering from Cesar Romero.</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>cesar@rfive.ai (R5)</managingEditor><atom:link href="https://rfive.ai/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Modernizing incrementally</title><link>https://rfive.ai/blog/modernizing-incrementally/</link><pubDate>Fri, 10 Jul 2026 00:00:00 +0000</pubDate><author>Cesar Romero</author><guid>https://rfive.ai/blog/modernizing-incrementally/</guid><description><![CDATA[<p>A client recently asked whether they should modernize their monolithic web application incrementally or rewrite it from scratch to make it work better with AI agents.</p>
<p>I think that framing is too limiting because it ties the destination to the journey.</p>
<p>The destination is usually clear: a modern backend API, a modern frontend that consumes it, and an MCP server that exposes the same capabilities to AI agents without going through a UI designed for humans.</p>]]></description></item></channel></rss>