<?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>DEV Community: Git Blame Nobody</title>
    <description>The latest articles on DEV Community by Git Blame Nobody (@git_blame_nobody).</description>
    <link>https://dev.to/git_blame_nobody</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4025005%2Fd05cecda-fd81-4aae-b6f1-cc2592501f90.png</url>
      <title>DEV Community: Git Blame Nobody</title>
      <link>https://dev.to/git_blame_nobody</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/git_blame_nobody"/>
    <language>en</language>
    <item>
      <title>I built a prompt engineering game — here's why I think learning by doing beats every tutorial</title>
      <dc:creator>Git Blame Nobody</dc:creator>
      <pubDate>Sat, 11 Jul 2026 10:00:18 +0000</pubDate>
      <link>https://dev.to/git_blame_nobody/i-built-a-prompt-engineering-game-heres-why-i-think-learning-by-doing-beats-every-tutorial-1gki</link>
      <guid>https://dev.to/git_blame_nobody/i-built-a-prompt-engineering-game-heres-why-i-think-learning-by-doing-beats-every-tutorial-1gki</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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3f5t83rovv1yr2y7jruo.png" 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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3f5t83rovv1yr2y7jruo.png" alt=" " width="800" height="360"&gt;&lt;/a&gt;&lt;br&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdm9idd37kw4izvm0e0fu.png" 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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdm9idd37kw4izvm0e0fu.png" alt=" " width="799" height="378"&gt;&lt;/a&gt;&lt;br&gt;
Every guide on prompt engineering teaches you theory.&lt;br&gt;
Read this, memorize that, here are 10 tips.&lt;/p&gt;

&lt;p&gt;The problem? You never actually write prompts.&lt;/p&gt;

&lt;p&gt;So I built a game: 10 challenges, each one forces you to &lt;br&gt;
use a specific technique — zero-shot, few-shot, chain of &lt;br&gt;
thought, role prompting, constraints, and more.&lt;/p&gt;

&lt;p&gt;You write a prompt → real LLM responds → second LLM &lt;br&gt;
evaluates whether you used the right technique. Not just &lt;br&gt;
whether the output looks okay — whether your prompt &lt;br&gt;
caused it correctly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Stack&lt;/strong&gt;: Next.js 14, Groq, Supabase, Upstash Redis, Vercel&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Try it free:&lt;/strong&gt; &lt;a href="https://dev.tourl"&gt;thepromptgame.vercel.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;What technique do you think is hardest to learn hands-on?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>showdev</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
