<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sai Kiran Reddy Uppula</title><description>Writing on software architecture, product engineering, and the decisions that survive contact with users. By Sai Kiran Reddy Uppula, a Full Stack Developer in Chicago.</description><link>https://blog.saikiranreddy.com/</link><language>en-us</language><atom:link href="https://blog.saikiranreddy.com/rss.xml" rel="self" type="application/rss+xml"/><item><title>Why clean architecture still matters for product MVPs</title><link>https://blog.saikiranreddy.com/posts/why-clean-architecture-still-matters-for-product-mvps/</link><guid isPermaLink="true">https://blog.saikiranreddy.com/posts/why-clean-architecture-still-matters-for-product-mvps/</guid><description>An architecture decision record on keeping domain boundaries in early product work, even when the team is small and the deadline is real.</description><pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate><category>architecture</category><category>mvp</category><category>product</category><category>engineering</category></item></channel></rss>