<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Musa Ndlala on Medium]]></title>
        <description><![CDATA[Stories by Musa Ndlala on Medium]]></description>
        <link>https://medium.com/@kmniroi?source=rss-bfbf2bfd179f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*liCTRCEtDBYyIeJMhlMxhA.png</url>
            <title>Stories by Musa Ndlala on Medium</title>
            <link>https://medium.com/@kmniroi?source=rss-bfbf2bfd179f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:42:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kmniroi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ The OWASP Top 10:2025 — But Make It Salesforce]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@kmniroi/the-owasp-top-10-2025-but-make-it-salesforce-a924fc6b4bb9?source=rss-bfbf2bfd179f------2"><img src="https://cdn-images-1.medium.com/max/1672/1*maxygchT3EIIpeyvLH26bg.png" width="1672"></a></p><p class="medium-feed-snippet">Musa Ndlala: this article is a bit late but better late than never</p><p class="medium-feed-link"><a href="https://medium.com/@kmniroi/the-owasp-top-10-2025-but-make-it-salesforce-a924fc6b4bb9?source=rss-bfbf2bfd179f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@kmniroi/the-owasp-top-10-2025-but-make-it-salesforce-a924fc6b4bb9?source=rss-bfbf2bfd179f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a924fc6b4bb9</guid>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[application-security]]></category>
            <dc:creator><![CDATA[Musa Ndlala]]></dc:creator>
            <pubDate>Mon, 13 Jul 2026 16:09:16 GMT</pubDate>
            <atom:updated>2026-07-13T16:09:16.717Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[ I Think My Technical Interview Was a Supply Chain Attack in Disguise]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@kmniroi/developer-interview-software-supply-chain-attack-npm-8cdf9d4c408b?source=rss-bfbf2bfd179f------2"><img src="https://cdn-images-1.medium.com/max/1376/1*l5JXG7QFFG1Bcqj2QQMO6w.png" width="1376"></a></p><p class="medium-feed-snippet">Musa Ndlala</p><p class="medium-feed-link"><a href="https://medium.com/@kmniroi/developer-interview-software-supply-chain-attack-npm-8cdf9d4c408b?source=rss-bfbf2bfd179f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@kmniroi/developer-interview-software-supply-chain-attack-npm-8cdf9d4c408b?source=rss-bfbf2bfd179f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8cdf9d4c408b</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[this-happened-to-me]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Musa Ndlala]]></dc:creator>
            <pubDate>Mon, 29 Jun 2026 07:52:35 GMT</pubDate>
            <atom:updated>2026-06-29T07:52:35.903Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[AI Writes the Code. But Who Owns the Architecture?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@kmniroi/ai-writes-the-code-but-who-owns-the-architecture-dd6de2cb3b1d?source=rss-bfbf2bfd179f------2"><img src="https://cdn-images-1.medium.com/max/1408/1*p0a1rTErtdvC3RNfQOdWiQ.png" width="1408"></a></p><p class="medium-feed-snippet">Why SOLID principles coupled with DSL toolbox are your last line of defence in an AI-first codebase!</p><p class="medium-feed-link"><a href="https://medium.com/@kmniroi/ai-writes-the-code-but-who-owns-the-architecture-dd6de2cb3b1d?source=rss-bfbf2bfd179f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@kmniroi/ai-writes-the-code-but-who-owns-the-architecture-dd6de2cb3b1d?source=rss-bfbf2bfd179f------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd6de2cb3b1d</guid>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[python-programming]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[solid-principles]]></category>
            <dc:creator><![CDATA[Musa Ndlala]]></dc:creator>
            <pubDate>Sun, 21 Jun 2026 08:38:58 GMT</pubDate>
            <atom:updated>2026-06-21T08:57:58.485Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[⚡ Build a Dynamic Blazor WebAssembly App for Salesforce CRUD (with a Generic REST API)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@kmniroi/build-a-dynamic-blazor-webassembly-app-for-salesforce-crud-with-a-generic-rest-api-ac92562f2435?source=rss-bfbf2bfd179f------2"><img src="https://cdn-images-1.medium.com/max/600/1*9OPZAcy4LdpmPKVfE5f15w.png" width="600"></a></p><p class="medium-feed-snippet">&#x201C;Why hardcode when you can empower your users with full dynamic control?&#x201D;</p><p class="medium-feed-link"><a href="https://medium.com/@kmniroi/build-a-dynamic-blazor-webassembly-app-for-salesforce-crud-with-a-generic-rest-api-ac92562f2435?source=rss-bfbf2bfd179f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@kmniroi/build-a-dynamic-blazor-webassembly-app-for-salesforce-crud-with-a-generic-rest-api-ac92562f2435?source=rss-bfbf2bfd179f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac92562f2435</guid>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[blazor-components]]></category>
            <category><![CDATA[salesforce-apex]]></category>
            <dc:creator><![CDATA[Musa Ndlala]]></dc:creator>
            <pubDate>Mon, 15 Jun 2026 08:12:11 GMT</pubDate>
            <atom:updated>2026-06-15T08:42:38.607Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Salesforce FlexCards + LWC: Why Rebuild When You Can Extend?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@kmniroi/salesforce-flexcards-lwc-why-rebuild-when-you-can-extend-f1118103d892?source=rss-bfbf2bfd179f------2"><img src="https://cdn-images-1.medium.com/max/1407/1*hV9XxCFspKyVFbVctG7t7g.png" width="1407"></a></p><p class="medium-feed-snippet">In enterprise development, there is a golden rule: Don&#x2019;t break what already works. Accelerate time-to-value.</p><p class="medium-feed-link"><a href="https://medium.com/@kmniroi/salesforce-flexcards-lwc-why-rebuild-when-you-can-extend-f1118103d892?source=rss-bfbf2bfd179f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@kmniroi/salesforce-flexcards-lwc-why-rebuild-when-you-can-extend-f1118103d892?source=rss-bfbf2bfd179f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1118103d892</guid>
            <category><![CDATA[salesforce-lwc]]></category>
            <category><![CDATA[salesforce-flexcards]]></category>
            <category><![CDATA[salesforce-omnistudio]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[low-code-development]]></category>
            <dc:creator><![CDATA[Musa Ndlala]]></dc:creator>
            <pubDate>Tue, 09 Jun 2026 18:02:15 GMT</pubDate>
            <atom:updated>2026-06-09T18:02:15.762Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[ Apex Sharing Keywords Demystified: with sharing, without sharing, and inherited sharing…]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@kmniroi/apex-sharing-keywords-demystified-with-sharing-without-sharing-and-inherited-sharing-35c2542535e5?source=rss-bfbf2bfd179f------2"><img src="https://cdn-images-1.medium.com/max/600/1*ooE7nzZqF8wl02o_XWAvJQ.png" width="600"></a></p><p class="medium-feed-snippet">Sharing keywords aren&#x2019;t syntax. They&#x2019;re security architecture.</p><p class="medium-feed-link"><a href="https://medium.com/@kmniroi/apex-sharing-keywords-demystified-with-sharing-without-sharing-and-inherited-sharing-35c2542535e5?source=rss-bfbf2bfd179f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@kmniroi/apex-sharing-keywords-demystified-with-sharing-without-sharing-and-inherited-sharing-35c2542535e5?source=rss-bfbf2bfd179f------2</link>
            <guid isPermaLink="false">https://medium.com/p/35c2542535e5</guid>
            <category><![CDATA[apex-sharing-keywords]]></category>
            <category><![CDATA[salesforce-security-model]]></category>
            <category><![CDATA[inherited-sharing]]></category>
            <category><![CDATA[salesforce-security]]></category>
            <category><![CDATA[enterprise-security]]></category>
            <dc:creator><![CDATA[Musa Ndlala]]></dc:creator>
            <pubDate>Sun, 31 May 2026 20:24:55 GMT</pubDate>
            <atom:updated>2026-05-31T20:24:55.201Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Salesforce : FlexCards vs LWC]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@kmniroi/salesforce-flexcards-vs-lwc-57c1a055dce5?source=rss-bfbf2bfd179f------2"><img src="https://cdn-images-1.medium.com/max/1024/1*yytfRK4JlpRMNb-8uxOXpQ.png" width="1024"></a></p><p class="medium-feed-snippet">A FlexCard is a metadata-driven UI component where you configure layouts and data sources with minimal code.A</p><p class="medium-feed-link"><a href="https://medium.com/@kmniroi/salesforce-flexcards-vs-lwc-57c1a055dce5?source=rss-bfbf2bfd179f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@kmniroi/salesforce-flexcards-vs-lwc-57c1a055dce5?source=rss-bfbf2bfd179f------2</link>
            <guid isPermaLink="false">https://medium.com/p/57c1a055dce5</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[vlocity]]></category>
            <category><![CDATA[salesforce-omnistudio]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[salesforce-lwc]]></category>
            <dc:creator><![CDATA[Musa Ndlala]]></dc:creator>
            <pubDate>Sun, 31 May 2026 18:46:06 GMT</pubDate>
            <atom:updated>2026-05-31T18:46:21.238Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Salesforce FlexCards: Why Didn’t I Just Build an LWC?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@kmniroi/salesforce-flexcards-why-didnt-i-just-build-an-lwc-69953565ee9b?source=rss-bfbf2bfd179f------2"><img src="https://cdn-images-1.medium.com/max/1672/1*A4xohef5G--WzeP3GInQhQ.png" width="1672"></a></p><p class="medium-feed-snippet">What if I told you that sometimes the fastest Salesforce component you&#x2019;ll ever build&#x2026;
is the one you never code?</p><p class="medium-feed-link"><a href="https://medium.com/@kmniroi/salesforce-flexcards-why-didnt-i-just-build-an-lwc-69953565ee9b?source=rss-bfbf2bfd179f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@kmniroi/salesforce-flexcards-why-didnt-i-just-build-an-lwc-69953565ee9b?source=rss-bfbf2bfd179f------2</link>
            <guid isPermaLink="false">https://medium.com/p/69953565ee9b</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[salesforce-omnistudio]]></category>
            <category><![CDATA[salesforce-lwc]]></category>
            <category><![CDATA[salesforce]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Musa Ndlala]]></dc:creator>
            <pubDate>Mon, 25 May 2026 08:36:00 GMT</pubDate>
            <atom:updated>2026-05-25T08:36:00.531Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Salesforce OmniStudio Integration Procedures Explained: Complete Guide to DataRaptors, HTTP…]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@kmniroi/salesforce-omnistudio-integration-procedures-explained-complete-guide-to-dataraptors-http-ba5c15bae231?source=rss-bfbf2bfd179f------2"><img src="https://cdn-images-1.medium.com/max/1041/1*IC8GincqgxbpQQNqgJ55QA.png" width="1041"></a></p><p class="medium-feed-snippet">Salesforce OmniStudio Integration Procedures Explained: From DataRaptors to Enterprise Architecture</p><p class="medium-feed-link"><a href="https://medium.com/@kmniroi/salesforce-omnistudio-integration-procedures-explained-complete-guide-to-dataraptors-http-ba5c15bae231?source=rss-bfbf2bfd179f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@kmniroi/salesforce-omnistudio-integration-procedures-explained-complete-guide-to-dataraptors-http-ba5c15bae231?source=rss-bfbf2bfd179f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba5c15bae231</guid>
            <category><![CDATA[salesforce-developer]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[vlocity]]></category>
            <category><![CDATA[omnistudio]]></category>
            <category><![CDATA[salesforce]]></category>
            <dc:creator><![CDATA[Musa Ndlala]]></dc:creator>
            <pubDate>Wed, 20 May 2026 08:51:00 GMT</pubDate>
            <atom:updated>2026-05-20T08:51:00.841Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to Build Scalable Salesforce Architecture: Introducing the SalesforceKlever DSL Framework for…]]></title>
            <link>https://medium.com/@kmniroi/how-to-build-scalable-salesforce-architecture-introducing-the-salesforceklever-dsl-framework-for-6e6ef614e13d?source=rss-bfbf2bfd179f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e6ef614e13d</guid>
            <category><![CDATA[salesforce-architecture]]></category>
            <category><![CDATA[salesforce-developer]]></category>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[apexdesignpatterns]]></category>
            <dc:creator><![CDATA[Musa Ndlala]]></dc:creator>
            <pubDate>Wed, 25 Mar 2026 17:41:10 GMT</pubDate>
            <atom:updated>2026-03-26T06:53:22.871Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Build Scalable Salesforce Architecture: Introducing the SalesforceKlever DSL Framework for Enterprise Teams</h3><p><strong>The Architect’s Shift:</strong> Why “Clean Code” Isn’t Enough for Growing Salesforce Engineering Teams</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*_WgNErlW5dOTnr_fQ6nQBA.png" /><figcaption>Author created image</figcaption></figure><h4>In Every Interview, There’s a Moment…</h4><p>After a couple of weeks riddled with back-to-back Salesforce interviews, something became very clear…<br>Not one interviewer was truly impressed by <em>just</em> code.</p><h4>They weren’t asking:</h4><blockquote>“Can you write Apex?”</blockquote><h4>They were asking — without saying it:</h4><blockquote>“What happens <strong>after</strong> you write the code?”</blockquote><ul><li>Can another developer maintain it?</li><li>Can a junior pick it up without calling you every hour?</li><li>Can an admin <em>eventually</em> understand and use it?</li></ul><p>And that’s when it hit me:</p><p>👉 Writing code is “easy”.<br>👉 Writing code that <strong>survives other humans</strong>… that’s the new frontier.</p><p><a href="https://github.com/mndlala/SFToolBox/tree/main/force-app/main/default/classes">SFToolBox/force-app/main/default/classes at main · mndlala/SFToolBox</a></p><h3>My Learning Strategy: Stay Curious, Stay Sharp</h3><h3>❓ What is this?</h3><p>A <strong>Salesforce DSL Framework (Developer Toolbox)</strong> — a reusable set of patterns that lets developers:</p><ul><li>Query data without writing raw SOQL</li><li>Execute async jobs without boilerplate</li><li>Make HTTP callouts in a clean, consistent way</li><li>Plug everything together using simple, readable syntax</li></ul><p>Think of it as:</p><blockquote>“A system where even a junior dev can build like a senior.” Hint Fluent Framework</blockquote><h3>📍 Where would you use it?</h3><ul><li>Enterprise orgs with multiple developers</li><li>Teams with high turnover or growing juniors</li><li>Projects where maintainability matters more than “quick wins”</li><li>Any org where admins might eventually interact with logic</li></ul><h3>Why would you use it?</h3><p>Because this is the reality:</p><blockquote>Code doesn’t fail in production because it doesn’t work.<br>It fails because no one understands it anymore, or has the time to figure it out.</blockquote><p>This framework solves:</p><ul><li>❌ messy SOQL scattered everywhere</li><li>❌ duplicated async logic</li><li>❌ inconsistent API callouts</li><li>❌ hard-to-test code</li></ul><p>And replaces it with:</p><ul><li>✅ reusable patterns</li><li>✅ consistent structure</li><li>✅ mockable architecture</li><li>✅ easy onboarding for new devs</li></ul><h3>⚙️ How would you use it?</h3><p>Instead of writing this:</p><pre>List&lt;Account&gt; accs = [SELECT Id, Name FROM Account WHERE Name LIKE &#39;%Test%&#39;];</pre><p>You write:</p><pre>// This looks easier to read right and familiar to devs <br>// from a dot net framework background<br><br>List&lt;SObject&gt; accs = Query <br>.fromKeyword(&#39;Account&#39;) <br>.selectFields(new List&lt;String&gt;{&#39;Id&#39;,&#39;Name&#39;}) <br>.whereClause(&#39;Name LIKE \&#39;%Test%\&#39;&#39;) <br>.limitKeyWord(10) <br>.execute();</pre><p>Instead of messy queueables:</p><pre>System.enqueueJob(new MyQueueableClass(...));</pre><h4>You write:</h4><pre>QueueDSL <br>.job(AccountService.class) <br>.withParams(new Map&lt;String, Object&gt;{ &#39;accountId&#39; =&gt; acc.Id }) <br>.dispatch();</pre><p>Instead of raw HTTP chaos:</p><pre>HttpRequest req = new HttpRequest(); <br>req.setEndpoint(&#39;callout:API&#39;); <br>req.setMethod(&#39;GET&#39;);</pre><h4>You write:</h4><pre>HttpDSL <br>.request() <br>.method(&#39;GET&#39;) <br>.endpoint(&#39;callout:MyAPI&#39;)<br>.send();</pre><h3>The Core Idea: Build a Developer Toolbox</h3><p>After those interviews, I stopped thinking:</p><blockquote>“How do I solve this problem?”</blockquote><p>And started thinking:</p><blockquote>“How do I make sure the next developer solves this problem faster than me?”</blockquote><p>So I built a <strong>framework</strong> with:</p><h3>🔹 Query DSL</h3><ul><li>Centralized SOQL</li><li>Clean, readable queries</li><li>Fully mockable</li></ul><h3>🔹 Queue DSL</h3><ul><li>One-line async execution</li><li>Parameter-driven jobs</li><li>Decoupled logic</li></ul><h3>🔹 HTTP DSL</h3><ul><li>Standardized integrations</li><li>Cleaner callouts</li><li>Easy to mock in tests</li></ul><h3>🔹 Interface-Based Design</h3><ul><li>Everything is injectable</li><li>Everything is testable</li><li>Nothing is tightly coupled</li></ul><h3>🧪 Testing Isn’t an Afterthought</h3><p>One of the biggest gaps I noticed in interviews:</p><blockquote>People write tests… but they don’t design for testing.</blockquote><p>This framework flips that.</p><p>Instead of forcing tests:</p><ul><li>You inject mocks</li><li>You isolate logic</li><li>You control behavior</li></ul><p>Example:</p><pre>Query<br>    .from(&#39;Account&#39;)<br>    .withExecutor(new MockQueryExecutor())<br>    .execute();</pre><p>👉 No real database needed.<br>👉 No brittle tests.<br>👉 Just clean validation.</p><h3>The Real Goal</h3><p>This wasn’t about being clever.</p><p>It was about solving a real problem:</p><blockquote>How do we make Salesforce development easier for the next person?</blockquote><p>Because in most projects:</p><ul><li>The original developer leaves</li><li>The code stays</li><li>The complexity grows</li></ul><p>And suddenly:</p><blockquote>Simple changes become “risky deployments”</blockquote><h3>⚠️ Gotchas</h3><p>Let’s keep it real — this approach isn’t magic.</p><h3>❗ Overengineering Risk</h3><p>If your org is small, this might feel heavy at first.</p><p>👉 But in growing teams? It pays off fast.</p><h3>❗ Learning Curve</h3><p>Junior devs need to:</p><ul><li>understand the DSL</li><li>not bypass it with raw Apex</li></ul><p>👉 Discipline matters.</p><h3>❗ Not a Silver Bullet</h3><p>You still need:</p><ul><li>good design decisions</li><li>proper data modeling</li><li>clear requirements</li></ul><p>This framework just makes execution cleaner.</p><h3>Final Thought</h3><p>After a week of interviews, one truth stood out:</p><blockquote>Writing code isn’t the hard part anymore.</blockquote><p>The hard part is:</p><ul><li>making it understandable</li><li>making it reusable</li><li>making it scalable across people</li></ul><p>So instead of writing code for <em>today</em>,<br>I started building systems for <em>whoever comes next</em>.</p><p>Because in the end:</p><blockquote>The best developers don’t just solve problems…<br>They make sure others can solve them too.</blockquote><p>That’s the <strong>SalesforceKlever way. 🚀</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*71WLQdB7qeW-j4SGm5IZuQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e6ef614e13d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>