<?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 BumbleB Technologies</title><link>https://bumbleb.co/tags/architecture/</link><description>Recent content in Architecture on BumbleB Technologies</description><generator>Hugo</generator><language>en-US</language><copyright>© 2024-2026 BumbleB Technologies Pvt. Ltd.</copyright><lastBuildDate>Mon, 22 Jun 2026 18:49:56 +0530</lastBuildDate><atom:link href="https://bumbleb.co/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Move the Reasoning Into the System</title><link>https://bumbleb.co/blog/2026-06-22-move-the-reasoning-into-the-system/</link><pubDate>Mon, 22 Jun 2026 08:00:00 +0530</pubDate><guid>https://bumbleb.co/blog/2026-06-22-move-the-reasoning-into-the-system/</guid><description>&lt;h1 id="move-the-reasoning-into-the-system">Move the Reasoning Into the System&lt;/h1>
&lt;h2 id="the-one-architectural-choice-that-everything-else-follows-from">The one architectural choice that everything else follows from&lt;/h2>
&lt;p>It is possible to argue for a product one feature at a time — cheaper questions here, a conversational interface there, a defensible architecture somewhere else — and never notice that the arguments are not separate. They can all be consequences of a single decision, made once, near the foundation, that propagates outward until it touches the price, the market, the moat, and the way the business grows. When that is true, the honest thing is to name the decision rather than its symptoms.&lt;/p></description></item></channel></rss>