<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" 
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Codekk Blog</title>
    <link>https://www.codekk.dev/blog</link>
    <description>Articles, tutorials, and insights about web development, UI design, and coding from the Codekk community.</description>
    <language>en-us</language>
    <lastBuildDate>Sat, 06 Jun 2026 09:16:44 GMT</lastBuildDate>
    <pubDate>Fri, 05 Jun 2026 03:12:33 GMT</pubDate>
    <ttl>60</ttl>
    <atom:link href="https://www.codekk.dev/blog/rss.xml" rel="self" type="application/rss+xml" />
    <image>
      <url>https://www.codekk.dev/logo.svg</url>
      <title>Codekk Blog</title>
      <link>https://www.codekk.dev/blog</link>
    </image>
    
    <item>
      <title>HTTP Status Codes Explained - What They Actually Mean and Why Developers Should Know Them</title>
      <link>https://www.codekk.dev/blog/http-status-codes-explained</link>
      <guid isPermaLink="true">https://www.codekk.dev/blog/http-status-codes-explained</guid>
      <pubDate>Fri, 05 Jun 2026 03:12:33 GMT</pubDate>
      <author>ssadie0416@gmail.com (Sadie Sink)</author>
      <description><![CDATA[Most developers know 200 and 404. But understanding the full range - and when to use them in your own APIs - makes you a noticeably better backend developer.]]></description>
      <content:encoded><![CDATA[
        <img src="https://res.cloudinary.com/dyswu0gin/image/upload/v1780629080/uifindr/components/u8h25ipw90iswbf0f1g9.jpg" alt="HTTP Status Codes Explained - What They Actually Mean and Why Developers Should Know Them" style="max-width: 100%; height: auto; margin-bottom: 20px;" />
        
        <hr style="margin: 30px 0;" />
        <p><a href="https://www.codekk.dev/blog/http-status-codes-explained">Read full article on Codekk</a></p>
      ]]></content:encoded>
      <category>status-codes</category>
      <category>http</category>
      <category>api</category>
      <category>backend</category>
      <enclosure url="https://res.cloudinary.com/dyswu0gin/image/upload/v1780629080/uifindr/components/u8h25ipw90iswbf0f1g9.jpg" type="image/jpeg" />
    </item>

    <item>
      <title>React vs Next.js: What&apos;s Actually Different and When to Use Which</title>
      <link>https://www.codekk.dev/blog/react-vs-nextjs</link>
      <guid isPermaLink="true">https://www.codekk.dev/blog/react-vs-nextjs</guid>
      <pubDate>Fri, 05 Jun 2026 02:22:47 GMT</pubDate>
      <author>ssadie0416@gmail.com (Sadie Sink)</author>
      <description><![CDATA[React and Next.js are often confused - one is a UI library, the other is a full framework built on top of it. This post breaks down the real differences: rendering strategies, routing, API routes, and when to pick one over the other.]]></description>
      <content:encoded><![CDATA[
        <img src="https://res.cloudinary.com/dyswu0gin/image/upload/v1780596753/uifindr/components/sg64dsmfouzygrhywj2y.jpg" alt="React vs Next.js: What&apos;s Actually Different and When to Use Which" style="max-width: 100%; height: auto; margin-bottom: 20px;" />
        
        <hr style="margin: 30px 0;" />
        <p><a href="https://www.codekk.dev/blog/react-vs-nextjs">Read full article on Codekk</a></p>
      ]]></content:encoded>
      <category>web-development</category>
      <category>nextjs</category>
      <category>react</category>
      <enclosure url="https://res.cloudinary.com/dyswu0gin/image/upload/v1780596753/uifindr/components/sg64dsmfouzygrhywj2y.jpg" type="image/jpeg" />
    </item>
  </channel>
</rss>