<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Vibe Coding Forem: seridarivus 13</title>
    <description>The latest articles on Vibe Coding Forem by seridarivus 13 (@seridarivus_13).</description>
    <link>https://vibe.forem.com/seridarivus_13</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3699213%2F07103e00-31c2-4352-a111-4bc354452099.jpg</url>
      <title>Vibe Coding Forem: seridarivus 13</title>
      <link>https://vibe.forem.com/seridarivus_13</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://vibe.forem.com/feed/seridarivus_13"/>
    <language>en</language>
    <item>
      <title>PLI 7.10 - Bypassing AI Knowledge Cutoffs with Auto-Data Synthesis</title>
      <dc:creator>seridarivus 13</dc:creator>
      <pubDate>Sat, 10 Jan 2026 20:51:33 +0000</pubDate>
      <link>https://vibe.forem.com/seridarivus_13/pli-710-bypassing-ai-knowledge-cutoffs-with-auto-data-synthesis-31pd</link>
      <guid>https://vibe.forem.com/seridarivus_13/pli-710-bypassing-ai-knowledge-cutoffs-with-auto-data-synthesis-31pd</guid>
      <description>&lt;p&gt;Hey everyone, I’m a student developer working on an alternative search/intelligence interface called PLI 7.10.&lt;/p&gt;

&lt;p&gt;The goal is to kill the SEO noise of modern search engines and the "knowledge cutoff" of standard LLMs. I’ve just implemented a "Self-Healing" logic that I’d love some architectural feedback on.&lt;/p&gt;

&lt;p&gt;The Logic: Instead of the AI simply saying "I don't know" when asked about recent events (e.g., Luke Littler’s 2026 stats), the backend now detects the failure and auto-triggers a &lt;a class="mentioned-user" href="https://dev.to/data"&gt;@data&lt;/a&gt; layer. It fetches, translates (via Google API), and ranks Wikipedia + YouTube context in one loop.&lt;/p&gt;

&lt;p&gt;Tech Specs &amp;amp; Trade-offs:&lt;/p&gt;

&lt;p&gt;Stack: Next.js / Node.js / Vercel.&lt;/p&gt;

&lt;p&gt;Latency: It’s about 20% slower than a standard hallucinating chat, but the accuracy for "live" data is significantly higher.&lt;/p&gt;

&lt;p&gt;Data Source: Uses a multi-language Wikipedia ranker to find the most "dense" info regardless of the user's language.&lt;/p&gt;

&lt;p&gt;Current Hurdles:&lt;/p&gt;

&lt;p&gt;Vercel Cold Starts: The multi-step scraping/translation layer is hitting some latency on the first hit.&lt;/p&gt;

&lt;p&gt;UX: Does a "3+1" card layout (Wiki + Video context) feel intuitive for a dev-tool, or is it too cluttered?&lt;/p&gt;

&lt;p&gt;Link: &lt;a href="https://pli7.vercel.app/" rel="noopener noreferrer"&gt;https://pli7.vercel.app/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>devops</category>
      <category>api</category>
      <category>tdd</category>
    </item>
    <item>
      <title>Why I built a search engine that limits results to exactly 4 items?!</title>
      <dc:creator>seridarivus 13</dc:creator>
      <pubDate>Thu, 08 Jan 2026 19:47:02 +0000</pubDate>
      <link>https://vibe.forem.com/seridarivus_13/why-i-built-a-search-engine-that-limits-results-to-exactly-4-items-4l08</link>
      <guid>https://vibe.forem.com/seridarivus_13/why-i-built-a-search-engine-that-limits-results-to-exactly-4-items-4l08</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ftmwrgjdbl8ttncts1dg1.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ftmwrgjdbl8ttncts1dg1.jpg" alt=" " width="800" height="1247"&gt;&lt;/a&gt;&lt;br&gt;
Researching a new topic usually means a messy workspace of Wikipedia tabs and YouTube tutorials. I built PLI 7.9 to fix that.&lt;/p&gt;

&lt;p&gt;🚀 The 3+1 Layout: Get the 3 most authoritative text sources and the top-rated video guide on a single, unified screen. ⚡ Sub-second Speed: Built on Vercel with smart API pooling for near-instant results. 🧼 Zero Noise: No ads, no 'suggested' distractions—just the data you need.&lt;/p&gt;

&lt;p&gt;Perfect for students, devs, and researchers who value their time. Try it here: &lt;a href="https://pli7.vercel.app" rel="noopener noreferrer"&gt;https://pli7.vercel.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>api</category>
    </item>
    <item>
      <title>Why I built a search engine that limits results to exactly 4 items</title>
      <dc:creator>seridarivus 13</dc:creator>
      <pubDate>Wed, 07 Jan 2026 20:54:23 +0000</pubDate>
      <link>https://vibe.forem.com/seridarivus_13/why-i-built-a-search-engine-that-limits-results-to-exactly-4-items-580c</link>
      <guid>https://vibe.forem.com/seridarivus_13/why-i-built-a-search-engine-that-limits-results-to-exactly-4-items-580c</guid>
      <description>&lt;p&gt;Tired of switching between Wiki and YouTube to learn something? I built PLI 7.9 to create a '3+1' learning dashboard. One search gives you the best 3 text deep-dives and the top video guide in one unified screen.&lt;/p&gt;

&lt;p&gt;Multimodal: Combines text, video, and image context instantly.&lt;/p&gt;

&lt;p&gt;Fast: Sub-second response times via Vercel and smart API pooling.&lt;/p&gt;

&lt;p&gt;Clean: Built for researchers, students, and devs who hate ads.&lt;/p&gt;

&lt;p&gt;Check the live version: &lt;a href="https://pli7.vercel.app" rel="noopener noreferrer"&gt;https://pli7.vercel.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>devops</category>
      <category>api</category>
    </item>
  </channel>
</rss>
