<?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 Livingstone- Full Stack Developer on Medium]]></title>
        <description><![CDATA[Stories by Livingstone- Full Stack Developer on Medium]]></description>
        <link>https://medium.com/@livingstonemaganya?source=rss-52951f7f3d4b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rufV9i1aA-e_BaN_u4Mkow.jpeg</url>
            <title>Stories by Livingstone- Full Stack Developer on Medium</title>
            <link>https://medium.com/@livingstonemaganya?source=rss-52951f7f3d4b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:58:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@livingstonemaganya/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[How I Shipped A Full-Stack Node.js App on Hostinger (And Survived My First Client)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/how-i-shipped-a-full-stack-node-js-app-on-hostinger-and-survived-my-first-client-21c22352ceb3?source=rss-52951f7f3d4b------2"><img src="https://cdn-images-1.medium.com/max/1024/1*VQsttjHTvh_zD6IDhYCfBw.png" width="1024"></a></p><p class="medium-feed-snippet">After 3 yrs of grinding code, landing my first client felt like a masterclass in easy money&#x200A;&#x2014;&#x200A;until his feedback crushed my design ego&#x2026;</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/how-i-shipped-a-full-stack-node-js-app-on-hostinger-and-survived-my-first-client-21c22352ceb3?source=rss-52951f7f3d4b------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/how-i-shipped-a-full-stack-node-js-app-on-hostinger-and-survived-my-first-client-21c22352ceb3?source=rss-52951f7f3d4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/21c22352ceb3</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[ecommerce-web-development]]></category>
            <category><![CDATA[nodejs-development]]></category>
            <dc:creator><![CDATA[Livingstone- Full Stack Developer]]></dc:creator>
            <pubDate>Wed, 04 Nov 2026 17:37:31 GMT</pubDate>
            <atom:updated>2026-11-05T11:50:46.823Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[They Vibe-Coded Adobe. Now Can We Please Stop Pretending Software Has Moats?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/they-vibe-coded-adobe-now-can-we-please-stop-pretending-software-has-moats-a65f2a8fa577?source=rss-52951f7f3d4b------2"><img src="https://cdn-images-1.medium.com/max/1264/1*ebq_n75SLcfIu3OTQgCgWw.jpeg" width="1264"></a></p><p class="medium-feed-snippet">Tech Twitter lost its mind this week, and vibe coders are having the best day of their lives, posting screenshots, victory laps, and&#x2026;</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/they-vibe-coded-adobe-now-can-we-please-stop-pretending-software-has-moats-a65f2a8fa577?source=rss-52951f7f3d4b------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/they-vibe-coded-adobe-now-can-we-please-stop-pretending-software-has-moats-a65f2a8fa577?source=rss-52951f7f3d4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a65f2a8fa577</guid>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Livingstone- Full Stack Developer]]></dc:creator>
            <pubDate>Thu, 15 Oct 2026 12:48:53 GMT</pubDate>
            <atom:updated>2026-10-15T15:15:05.994Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I Thought React Would Save Me From map, filter, and reduce. Boy, was I Wrong.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/i-thought-react-would-save-me-from-map-filter-and-reduce-boy-was-i-wrong-002dc1239eb3?source=rss-52951f7f3d4b------2"><img src="https://cdn-images-1.medium.com/max/1264/1*pxltIbqOrkZmVedTrcW1HQ.jpeg" width="1264"></a></p><p class="medium-feed-snippet">Nobody warned me that learning React meant learning map again, but this time with JSX and more crying.</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/i-thought-react-would-save-me-from-map-filter-and-reduce-boy-was-i-wrong-002dc1239eb3?source=rss-52951f7f3d4b------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/i-thought-react-would-save-me-from-map-filter-and-reduce-boy-was-i-wrong-002dc1239eb3?source=rss-52951f7f3d4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/002dc1239eb3</guid>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Livingstone- Full Stack Developer]]></dc:creator>
            <pubDate>Thu, 15 Oct 2026 12:48:40 GMT</pubDate>
            <atom:updated>2026-10-15T12:48:40.437Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I Thought My Express Auth Was Secure Until I Tried Hijacking My Own Account]]></title>
            <link>https://livingstonemaganya.medium.com/i-thought-my-express-auth-was-secure-until-i-tried-hijacking-my-own-account-822f68682be1?source=rss-52951f7f3d4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/822f68682be1</guid>
            <category><![CDATA[session-hijacking]]></category>
            <category><![CDATA[express-authentication]]></category>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[javascript-security]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Livingstone- Full Stack Developer]]></dc:creator>
            <pubDate>Fri, 09 Oct 2026 08:42:31 GMT</pubDate>
            <atom:updated>2026-10-09T08:42:31.612Z</atom:updated>
            <content:encoded><![CDATA[<h4>What testing my npm package @maganya/cross-cookie taught me about cookie serialization vs. session integrity.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1fvgMBzrgryRBZe7xxdxEA.png" /></figure><p>When building web applications, it’s easy to feel confident once your database queries are parameterized and your cookies have flags like HttpOnly and SameSite=Strict.</p><p>To cut the long story short, I built a <a href="https://medium.com/@livingstonemaganya/i-tested-my-npm-package-in-a-real-production-stack-0f7ca5f4ad2a">Express + PostgreSQL project</a> specifically to battle-test my npm package, <a href="https://javascript.plainenglish.io/i-stopped-copy-pasting-code-and-built-my-own-npm-package-heres-what-broke-and-how-i-fixed-it-3fce57ee48b4">@maganya/cross-cookie, </a>a lightweight utility for parsing and serializing HTTP cookies.</p><p>The package worked as intended, and my SQL queries were 100% safe from injection. But while inspecting the HTTP headers in DevTools, I realized I had left a critical security vulnerability wide open in my application logic.</p><h3>The Initial Setup: SQL Injection Proof, but…</h3><p>My database queries used tagged template literals (dbSELECT * FROM users WHERE email = ${email}``), which automatically parameterized all inputs. SQL injection was impossible.</p><p>For authentication, I parsed and serialized session cookies using @maganya/cross-cookie:</p><pre>// Storing user identity directly in the cookie<br>const sessionCookie = serializeCookie(&#39;session_user&#39;, user.email, {<br>  httpOnly: true,<br>  secure: process.env.NODE_ENV === &#39;production&#39;,<br>  sameSite: &#39;Strict&#39;,<br>  path: &#39;/&#39;,<br>  maxAge: 86400 // 24 hours<br>});<br><br>res.setHeader(&#39;Set-Cookie&#39;, sessionCookie);</pre><p>On paper, this looked clean. httpOnly: true meant client-side JavaScript couldn&#39;t read document.cookie, protecting against XSS attacks.</p><h3>The Lightbulb Moment: Cookie Serialization ≠ Session Integrity</h3><p>Here’s the catch: <strong>httpOnly prevents JavaScript from reading cookies, but it does NOT stop users or tools from modifying outgoing request headers.</strong></p><p>To test this, I opened browser DevTools, edited the session_user cookie value from my email to victim@example.com, and refreshed /dashboard.</p><p>Because my backend blindly trusted the string inside cookies[&#39;session_user&#39;], the server granted me full access to that victim&#39;s account without requiring a password.</p><h3>The Key Lesson</h3><ul><li><strong>Cookie Serialization (what </strong><strong>@maganya/cross-cookie does):</strong> Ensures HTTP headers are formatted correctly with safety attributes like HttpOnly, SameSite, and Secure.</li><li><strong>Session Integrity (what the application must do):</strong> Ensures the value <em>inside</em> the cookie is an unguessable token verified against a trusted server store.</li></ul><h3>How I Fixed It: Database-Backed Session Tokens</h3><p>To solve this, I shifted from <strong>stateless client trust</strong> to <strong>stateful server-side sessions</strong>.</p><h3>Step 1: The PostgreSQL sessions Table</h3><p>First, I created a dedicated table to store active session tokens:</p><pre>CREATE TABLE IF NOT EXISTS sessions (<br>  id SERIAL PRIMARY KEY,<br>  user_id INTEGER REFERENCES users(id) ON DELETE CASCADE,<br>  token VARCHAR(255) NOT NULL UNIQUE,<br>  expires_at TIMESTAMPTZ NOT NULL,<br>  created_at TIMESTAMPTZ DEFAULT CURRENT_TIMESTAMP<br>);</pre><h3>Step 2: Generating Random Tokens on Login</h3><p>Instead of placing user.email in the cookie, I generated a 256-bit cryptographically secure random token using Node&#39;s built-in crypto module:</p><pre>import crypto from &#39;node:crypto&#39;;<br><br>// 1. Generate an unguessable token<br>const sessionToken = crypto.randomBytes(32).toString(&#39;hex&#39;);<br>const expiresAt = new Date(Date.now() + 24 * 60 * 60 * 1000);<br><br>// 2. Persist in PostgreSQL<br>await db`<br>  INSERT INTO sessions (user_id, token, expires_at)<br>  VALUES (${user.id}, ${sessionToken}, ${expiresAt})<br>`;<br><br>// 3. Serialize ONLY the random token into the cookie<br>const sessionCookie = serializeCookie(&#39;session_token&#39;, sessionToken, {<br>  httpOnly: true,<br>  secure: process.env.NODE_ENV === &#39;production&#39;,<br>  sameSite: &#39;Strict&#39;,<br>  path: &#39;/&#39;,<br>  maxAge: 86400<br>});<br><br>res.setHeader(&#39;Set-Cookie&#39;, sessionCookie);</pre><h3>Step 3: Validating Tokens in Middleware</h3><p>Now, when a user accesses a protected route, the requireAuth middleware joins sessions with users to verify the token:</p><pre>export async function requireAuth(req, res, next) {<br>  const cookies = parseCookies(req.headers.cookie || &#39;&#39;);<br>  const token = cookies[&#39;session_token&#39;];<br><br>  if (!token) return res.redirect(&#39;/login&#39;);<br><br>  const sessions = await db`<br>    SELECT s.token, u.id, u.email, u.full_name<br>    FROM sessions s<br>    JOIN users u ON s.user_id = u.id<br>    WHERE s.token = ${token} AND s.expires_at &gt; NOW()<br>  `;<br><br>  if (sessions.length === 0) return res.redirect(&#39;/login&#39;);<br><br>  req.user = sessions[0];<br>  next();<br>}</pre><p>Now, if a user modifies their cookie string in DevTools, the lookup in sessions fails, and they are redirected back to /login.</p><h3>Conclusion</h3><p>Testing npm packages in real projects rather than isolated unit tests always uncovers unexpected real-world edge cases. And yes, I’m constantly learning from this project which I got to say, ended up being a much larger project than I thought.</p><p>Using @maganya/cross-cookie made serializing and parsing HTTP headers effortless, but combining it with server-side database tokens was what actually secured the application.</p><p>If you are building authentication in Express:</p><ol><li>Use tagged template literals / parameterized queries for SQL security.</li><li>Use @maganya/cross-cookie for clean HTTP header handling.</li><li><strong>Never trust raw identity data stored in cookies.</strong> Always back session cookies with unguessable tokens verified on the server.</li></ol><h3>Resources</h3><ul><li><strong>NPM Package:</strong> @maganya/cross-cookie</li><li><strong>GitHub Repository:</strong> <em>(</em><a href="https://github.com/LivingstoneMaganya/dashboard"><em>Dashboard On Github</em></a><em>)</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=822f68682be1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Tested My npm Package in a Real Production Stack]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/i-tested-my-npm-package-in-a-real-production-stack-0f7ca5f4ad2a?source=rss-52951f7f3d4b------2"><img src="https://cdn-images-1.medium.com/max/1536/1*BUzhOXsCaXutku66TX3VxQ.png" width="1536"></a></p><p class="medium-feed-snippet">I built a full-stack dashboard with Express, EJS, and Neon PostgreSQL to test my npm in production.</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/i-tested-my-npm-package-in-a-real-production-stack-0f7ca5f4ad2a?source=rss-52951f7f3d4b------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/i-tested-my-npm-package-in-a-real-production-stack-0f7ca5f4ad2a?source=rss-52951f7f3d4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/0f7ca5f4ad2a</guid>
            <category><![CDATA[cookie-handling]]></category>
            <category><![CDATA[npm-package]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[neon-postgresql]]></category>
            <category><![CDATA[session-management]]></category>
            <dc:creator><![CDATA[Livingstone- Full Stack Developer]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 21:08:33 GMT</pubDate>
            <atom:updated>2026-10-08T21:08:33.637Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I Stopped Copy-Pasting Code and Built My Own npm Package. Here’s What Broke (and How I Fixed It)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/i-stopped-copy-pasting-code-and-built-my-own-npm-package-heres-what-broke-and-how-i-fixed-it-3fce57ee48b4?source=rss-52951f7f3d4b------2"><img src="https://cdn-images-1.medium.com/max/1264/1*7o-QpZjgvy1KtENyDbwAxw.jpeg" width="1264"></a></p><p class="medium-feed-snippet">Real-world hurdles, ESM/CJS build errors, and architectural lessons from building and publishing a cross-runtime TypeScript utility to npm.</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/i-stopped-copy-pasting-code-and-built-my-own-npm-package-heres-what-broke-and-how-i-fixed-it-3fce57ee48b4?source=rss-52951f7f3d4b------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/i-stopped-copy-pasting-code-and-built-my-own-npm-package-heres-what-broke-and-how-i-fixed-it-3fce57ee48b4?source=rss-52951f7f3d4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fce57ee48b4</guid>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Livingstone- Full Stack Developer]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 13:42:17 GMT</pubDate>
            <atom:updated>2026-10-08T13:42:17.552Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I Audited a Developer Blog and Found 2.4MB of Inline Base64 Images. Here’s How I Fixed It.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/i-audited-a-developer-blog-and-found-2-4mb-of-inline-base64-images-heres-how-i-fixed-it-0743dd0053d1?source=rss-52951f7f3d4b------2"><img src="https://cdn-images-1.medium.com/max/1424/1*AEzGuQpGdAOdd6nWqszrXA.png" width="1424"></a></p><p class="medium-feed-snippet">We&#x2019;ve all taken shortcuts for the sake of &#x201C;simplicity.&#x201D; And yes, I&#x2019;m also guilty of this crime. But for some reason, it always comes back&#x2026;</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/i-audited-a-developer-blog-and-found-2-4mb-of-inline-base64-images-heres-how-i-fixed-it-0743dd0053d1?source=rss-52951f7f3d4b------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/i-audited-a-developer-blog-and-found-2-4mb-of-inline-base64-images-heres-how-i-fixed-it-0743dd0053d1?source=rss-52951f7f3d4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/0743dd0053d1</guid>
            <category><![CDATA[web-performance]]></category>
            <category><![CDATA[page-speed]]></category>
            <category><![CDATA[base64]]></category>
            <category><![CDATA[core-web-vitals]]></category>
            <category><![CDATA[image-optimization]]></category>
            <dc:creator><![CDATA[Livingstone- Full Stack Developer]]></dc:creator>
            <pubDate>Tue, 06 Oct 2026 17:23:35 GMT</pubDate>
            <atom:updated>2026-10-06T17:23:35.411Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why You Shouldn’t Learn React First: A Full-Stack Developer’s Guide to the Modern Job Market]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/why-you-shouldnt-learn-react-first-a-full-stack-developer-s-guide-to-the-modern-job-market-5e4891eee9b8?source=rss-52951f7f3d4b------2"><img src="https://cdn-images-1.medium.com/max/1024/1*KUot9px537u8LmRR4_DzOA.png" width="1024"></a></p><p class="medium-feed-snippet">Why learning backend architecture and SQL before React builds a future-proof engineering career in the age of AI.</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/why-you-shouldnt-learn-react-first-a-full-stack-developer-s-guide-to-the-modern-job-market-5e4891eee9b8?source=rss-52951f7f3d4b------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/why-you-shouldnt-learn-react-first-a-full-stack-developer-s-guide-to-the-modern-job-market-5e4891eee9b8?source=rss-52951f7f3d4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e4891eee9b8</guid>
            <category><![CDATA[full-stack-web-developer]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <dc:creator><![CDATA[Livingstone- Full Stack Developer]]></dc:creator>
            <pubDate>Tue, 06 Oct 2026 17:14:52 GMT</pubDate>
            <atom:updated>2026-10-07T08:39:27.721Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How AI-Generated Web UI Breeds Invisible Bounce Rates and Kills SaaS Conversions]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://livingstonemaganya.medium.com/how-ai-generated-web-ui-breeds-invisible-bounce-rates-and-kills-saas-conversions-27672b35415a?source=rss-52951f7f3d4b------2"><img src="https://cdn-images-1.medium.com/max/1600/1*D1XQ8OJ2ZX-nVS2C5qAAzg.png" width="1600"></a></p><p class="medium-feed-snippet">Your AI-built landing page loads fast, passes every accessibility check, and looks finished. So why are visitors leaving in seconds?</p><p class="medium-feed-link"><a href="https://livingstonemaganya.medium.com/how-ai-generated-web-ui-breeds-invisible-bounce-rates-and-kills-saas-conversions-27672b35415a?source=rss-52951f7f3d4b------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://livingstonemaganya.medium.com/how-ai-generated-web-ui-breeds-invisible-bounce-rates-and-kills-saas-conversions-27672b35415a?source=rss-52951f7f3d4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/27672b35415a</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ai-web-design]]></category>
            <category><![CDATA[conversion-rate-saas]]></category>
            <category><![CDATA[ai-generated-ui]]></category>
            <category><![CDATA[bounce-rate]]></category>
            <dc:creator><![CDATA[Livingstone- Full Stack Developer]]></dc:creator>
            <pubDate>Sat, 03 Oct 2026 17:42:41 GMT</pubDate>
            <atom:updated>2026-10-04T11:37:50.184Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why Google Gemini Is Clearly Winning the AI Race]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/why-google-gemini-is-clearly-winning-the-ai-race-857dfb30d481?source=rss-52951f7f3d4b------2"><img src="https://cdn-images-1.medium.com/max/2400/1*YwkOqwkweL1jxUj1bO2-pQ.png" width="2400"></a></p><p class="medium-feed-snippet">Independent AI startups burnt through billions in venture capital to prove that consumers wanted chatbots. Google simply watched, waited&#x2026;</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/why-google-gemini-is-clearly-winning-the-ai-race-857dfb30d481?source=rss-52951f7f3d4b------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/why-google-gemini-is-clearly-winning-the-ai-race-857dfb30d481?source=rss-52951f7f3d4b------2</link>
            <guid isPermaLink="false">https://medium.com/p/857dfb30d481</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[google-gemini]]></category>
            <dc:creator><![CDATA[Livingstone- Full Stack Developer]]></dc:creator>
            <pubDate>Sat, 03 Oct 2026 12:06:29 GMT</pubDate>
            <atom:updated>2026-10-03T14:12:19.641Z</atom:updated>
        </item>
    </channel>
</rss>