<?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 Brayce Dominic on Medium]]></title>
        <description><![CDATA[Stories by Brayce Dominic on Medium]]></description>
        <link>https://medium.com/@braycedominic11?source=rss-18c628031d5d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*NrBN4-wgaDnYwTD1</url>
            <title>Stories by Brayce Dominic on Medium</title>
            <link>https://medium.com/@braycedominic11?source=rss-18c628031d5d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:17:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@braycedominic11/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[This year taught me something load balancers have known forever:
never route all the pressure to a…]]></title>
            <link>https://medium.com/@braycedominic11/this-year-taught-me-something-load-balancers-have-known-forever-never-route-all-the-pressure-to-a-c665e4a49606?source=rss-18c628031d5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c665e4a49606</guid>
            <dc:creator><![CDATA[Brayce Dominic]]></dc:creator>
            <pubDate>Wed, 31 Dec 2025 20:23:07 GMT</pubDate>
            <atom:updated>2025-12-31T20:23:07.226Z</atom:updated>
            <content:encoded><![CDATA[<h3>This year taught me something load balancers have known forever:<br>never route all the pressure to a single point.<br>At the start of the year, I unknowingly designed myself like a poorly architected system.<br>One server. No replicas. No redundancy.<br>I handled everything alone, <br>every task,<br>every deadline,<br>every decision.<br>At first, it seemed efficient. Requests were flowing. Progress was visible.<br>But just like in real systems, traffic didn’t stay predictable.<br>The load increased.<br>Context switching became expensive.<br>Small failures started compounding.<br>Eventually, the system behaved exactly as expected under poor design:<br>responses slowed, requests dropped, and some processes failed entirely.<br>That’s when load balancing stopped being a textbook concept and became a lived experience.<br>I realized that sustainable systems don’t scale by pushing one component harder.<br>They scale by distributing responsibility, isolating failure, and designing for recovery.<br>So I changed how I worked:<br>I stopped treating everything as a single monolith<br>I broke work into independent, manageable modules<br>I learned to delegate instead of bottleneck<br>I planned fallbacks instead of hoping nothing would go wrong<br>The result wasn’t just better productivity, it was stability.<br>Software engineering quietly taught me a life principle I won’t forget: If everything depends on you, the system isn’t strong, it’s fragile.<br>I’m ending the year more balanced.<br>Not because the load disappeared,<br>but because it’s finally distributed, both in architecture and in life.<br>#SoftwareEngineering #LoadBalancing #SystemsThinking #YearInReview #Growth</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c665e4a49606" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I finally understood “Sign in with Google” after watching someone enter a building.]]></title>
            <link>https://medium.com/@braycedominic11/i-finally-understood-sign-in-with-google-after-watching-someone-enter-a-building-bf19f37b73a6?source=rss-18c628031d5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf19f37b73a6</guid>
            <dc:creator><![CDATA[Brayce Dominic]]></dc:creator>
            <pubDate>Mon, 29 Dec 2025 20:16:37 GMT</pubDate>
            <atom:updated>2025-12-29T20:16:37.651Z</atom:updated>
            <content:encoded><![CDATA[<p>I finally understood “Sign in with Google” after watching someone enter a building.</p><p>Today I watched a visitor enter an office building.<br>He didn’t explain who he was.<br>He didn’t fill long forms.<br>He just showed his National ID at the gate.<br>The guard looked at the ID, nodded, and let him in.<br>That’s exactly how “Sign in with Google” works.</p><p>Your app is the building.<br>Google is the government issuing IDs.<br>You don’t ask for the person’s life story — you trust the ID.<br>When someone signs in with Google, your app is saying:<br>“I trust Google to confirm who you are.”</p><p>But when someone signs in with email and password, your app becomes:<br>the ID office<br>the security system<br>the recovery desk<br>and the guard<br>More responsibility. More risk.</p><p>Software engineering becomes easy when we stop memorizing terms and start relating them to real life.<br>That’s how I learn.<br>That’s how I build.<br><br>#SoftwareEngineering #SystemDesign #OAuth #LearningByDoing #TechExplained</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aI16grDkFmaXrGySknFaBw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BnyaUBaP22j0zWl-DDyAUQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf19f37b73a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You Clicked “Login” — A Tiny Story You Never See
Imagine this.]]></title>
            <link>https://medium.com/@braycedominic11/you-clicked-login-a-tiny-story-you-never-see-imagine-this-338c43ee80b0?source=rss-18c628031d5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/338c43ee80b0</guid>
            <dc:creator><![CDATA[Brayce Dominic]]></dc:creator>
            <pubDate>Sun, 28 Dec 2025 22:00:18 GMT</pubDate>
            <atom:updated>2025-12-28T22:00:18.229Z</atom:updated>
            <content:encoded><![CDATA[<h3>You Clicked “Login” — A Tiny Story You Never See<br>Imagine this.<br>You’re standing outside a building.<br>You knock once.<br>The door opens immediately.<br>You don’t think about:<br>Who checked your name<br>Who verified your ID<br>Who unlocked the door<br>You just walk in.<br>That’s exactly what happens when you tap Login in an app.<br>Your phone quietly knocks on another computer far away.<br>That computer checks your name.<br>It checks your password.<br>It checks if you’re allowed in.<br>Then it opens the door.<br>All of this happens so fast that it feels like magic.<br>But it’s not magic.<br>It’s software engineers designing systems so smooth you never notice them.<br>The best technology is invisible.<br>You only notice it when it doesn’t work.<br>Next time an app lets you in instantly,<br>remember the tiny digital conversation that just happened for you.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/1*cVVFYY37hDu6RlwS2QBQAQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=338c43ee80b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Day My App Finally Trusted Its Users (A JWT Story)]]></title>
            <link>https://medium.com/@braycedominic11/the-day-my-app-finally-trusted-its-users-a-jwt-story-68775edf8a0e?source=rss-18c628031d5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/68775edf8a0e</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[json-web-token]]></category>
            <category><![CDATA[backend-development]]></category>
            <dc:creator><![CDATA[Brayce Dominic]]></dc:creator>
            <pubDate>Mon, 22 Dec 2025 19:36:31 GMT</pubDate>
            <atom:updated>2025-12-22T19:36:31.436Z</atom:updated>
            <content:encoded><![CDATA[<p>The Day My App Finally Trusted Its Users (A JWT Story)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F5AowwknWxkMCJIkS3GcMQ.gif" /><figcaption>JSON Web Token Architecture</figcaption></figure><p>At first, my app was paranoid.<br>Every click, every request, it kept asking:<br>“Who are you?”<br>“Are you logged in?”<br>“Prove it again.”</p><p>Then I met JWT.</p><p>Instead of checking the database on every request, the server said:<br>“Here’s a token. Guard it well. Come back with it when you need access.”</p><p>That token had a story inside it:<br>🔹 Who the user is<br>🔹 What they’re allowed to do<br>🔹 When the trust expires</p><p>And the magic part?<br>The server didn’t need to remember anything.<br>If the signature was valid, trust was earned.</p><p>Suddenly my app became:<br>⚡ Faster<br>📈 Scalable<br>🔐 More secure</p><p>But JWT also taught me responsibility.<br>Because trust should never last forever.</p><p>So I learned to:<br>✔ Set expirations<br>✔ Protect tokens like secrets<br>✔ Never expose sensitive data</p><p>JWT isn’t just authentication.<br>It’s a contract of trust between a user and a system.</p><p>Still learning. Still building. Still securing. 🚀</p><p>#JWT #SoftwareEngineering #BackendDevelopment #APIs #LearningInPublic #WebSecurity #Developers</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68775edf8a0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>