<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Kueri.me</title>
  <link>https://kueri.me/</link>
  <description>Code, craft, and digital curiosity.</description>
  <language>en</language>
  <lastBuildDate>Wed, 30 Sep 2026 00:36:19 GMT</lastBuildDate>
  <atom:link href="https://kueri.me/feed.xml" rel="self" type="application/rss+xml"/>
  <item>
    <title>I Built the Same App Three Times in Three Frameworks. Here&#039;s What a Year Taught Me.</title>
    <link>https://kueri.me/javascript-framework-comparison-year-long-experiment/</link>
    <guid isPermaLink="true">https://kueri.me/javascript-framework-comparison-year-long-experiment/</guid>
    <description>Chasing the hottest JavaScript framework feels like a developer rite of passage, but what does it actually cost you in time, sanity, and shipping velocity? After spending a year deliberately building the same feature set across three different frameworks, I have some thoughts — and not all of them are flattering to the shiny new thing.</description>
    <author>Kueri.me</author>
    <category>Opinion &amp; Retrospectives</category>
    <pubDate>Wed, 30 Sep 2026 00:31:00 GMT</pubDate>
  </item>
  <item>
    <title>The Repo Graveyard: What Your Abandoned Projects Are Actually Trying to Tell You</title>
    <link>https://kueri.me/repo-graveyard-abandoned-side-projects-lessons/</link>
    <guid isPermaLink="true">https://kueri.me/repo-graveyard-abandoned-side-projects-lessons/</guid>
    <description>Most developers have a GitHub profile that looks less like a portfolio and more like a digital cemetery. Before you start your next side project, it&#039;s worth understanding exactly why the last five are collecting dust — and what you can do differently this time.</description>
    <author>Kueri.me</author>
    <category>Developer Culture</category>
    <pubDate>Wed, 30 Sep 2026 00:31:00 GMT</pubDate>
  </item>
</channel>
</rss>