<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on cloudmato.com</title><link>https://cloudmato.com/tags/architecture/</link><description>Recent content in Architecture on cloudmato.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cloudmato.com</managingEditor><webMaster>cloudmato.com</webMaster><lastBuildDate>Sun, 07 Jun 2026 15:51:49 +0530</lastBuildDate><atom:link href="https://cloudmato.com/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Why SOLID Principles Matter &amp; Why Developers Skip Them</title><link>https://cloudmato.com/posts/solid-principles-real-world-examples/</link><pubDate>Sun, 07 Jun 2026 15:51:49 +0530</pubDate><author>cloudmato.com</author><guid>https://cloudmato.com/posts/solid-principles-real-world-examples/</guid><description>&lt;p&gt;Everyone talks about SOLID principles. Your senior dev mentions them in code review. Your architecture docs reference them. But why do actual projects become unmaintainable garbage despite teams &amp;ldquo;knowing&amp;rdquo; SOLID? The answer: understanding SOLID and actually building with it are two completely different things [1].&lt;/p&gt;
&lt;p&gt;Most developers learn about SOLID early, nod along, then immediately violate these principles the moment a deadline hits. Let me show you where the rubber meets the road — and why it&amp;rsquo;s harder than it sounds.&lt;/p&gt;</description></item></channel></rss>