<?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: Jeet Singh</title>
    <description>The latest articles on DEV Community by Jeet Singh (@jeet_singh_63644d9175a9f6).</description>
    <link>https://dev.to/jeet_singh_63644d9175a9f6</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%2F3573564%2F3ca4955d-9f60-430f-985b-f99c7dd1690c.png</url>
      <title>DEV Community: Jeet Singh</title>
      <link>https://dev.to/jeet_singh_63644d9175a9f6</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jeet_singh_63644d9175a9f6"/>
    <language>en</language>
    <item>
      <title>Paper Walk: Print a Card, Leave Your Phone, Go Outside</title>
      <dc:creator>Jeet Singh</dc:creator>
      <pubDate>Fri, 09 Oct 2026 02:50:43 +0000</pubDate>
      <link>https://dev.to/jeet_singh_63644d9175a9f6/paper-walk-print-a-card-leave-your-phone-go-outside-14ak</link>
      <guid>https://dev.to/jeet_singh_63644d9175a9f6/paper-walk-print-a-card-leave-your-phone-go-outside-14ak</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week1-2026-10-05"&gt;Hacktoberfest Open-Source AI Challenge Week 1: Touch Grass&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Paper Walk&lt;/strong&gt; is a small web page that makes a printable walk card. You choose how much time you have (10 minutes, 30 minutes or an hour), where you are (home, street, park, water or forest), your area, and how you feel. A small open-weight model running on your own computer writes a few short prompts such as "Find three different shades of green" or "Listen for the farthest sound you can hear."&lt;/p&gt;

&lt;p&gt;You print the card, put your phone in your pocket, and go. The screen part takes about a minute and the rest happens in the world, so the screen really is the shortest part of the experience.&lt;/p&gt;

&lt;p&gt;After the walk you can save a one-line note about what you noticed. The next card builds on your earlier notes and avoids repeating them.&lt;/p&gt;

&lt;p&gt;It's for anyone who is bored at home or stuck in a screen habit and wants a small, low-effort reason to look around. I built it for myself first, in Patna, Bihar.&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/rK9d1lwIiAc" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/jeetsingh008/PaperWalk" rel="noopener noreferrer"&gt;https://github.com/jeetsingh008/PaperWalk&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It's a single HTML file with no dependencies. Run it with Ollama and a small model; the steps are in the README.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Model:&lt;/strong&gt; &lt;code&gt;gemma3:1b&lt;/code&gt;, an open-weight model, run locally with Ollama.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;App:&lt;/strong&gt; one HTML file with plain JavaScript. It sends your choices (time, place, area, mood, and your last five walk notes) to Ollama's local API and turns the reply into a printable card.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fallback:&lt;/strong&gt; if no model is running, the page uses a small built-in list of prompts, so it still works offline.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Memory:&lt;/strong&gt; walk notes are saved in the browser's local storage and never leave the device.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The hard part was the model, not the code. My first version produced prompts with invented details, like a faded tiger mural on a wall near me, because a 1B-parameter model can't see my surroundings and simply guesses. It also ignored my "bored at home" setting at first. Telling it what &lt;em&gt;not&lt;/em&gt; to do barely helped, but giving it a few examples of the style I wanted worked much better. The final card gave plain prompts like "Find something smooth, gray, slightly damp" that work anywhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Does Open Innovation Matter?
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;It runs on my laptop with no account and no cost.&lt;/strong&gt; I don't need an API key or a subscription to use it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;My walk notes stay on my device.&lt;/strong&gt; Notes about where I am and what I do each day are personal, and with a local model they never go to a server I don't control.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;I could change the model.&lt;/strong&gt; When the 1B model gave weak results, I could try different settings and prompts, and a bigger model would be a one-word change in the page. With a closed API I would be stuck with whatever the provider offers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The tradeoff is real.&lt;/strong&gt; A tiny local model is private and free but sometimes awkward, as with "the distance of a distant, slightly rumbling vehicle." For this project that was an acceptable price.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
    </item>
    <item>
      <title>This was a feature not a bug🐞</title>
      <dc:creator>Jeet Singh</dc:creator>
      <pubDate>Sun, 19 Oct 2025 08:52:50 +0000</pubDate>
      <link>https://dev.to/jeet_singh_63644d9175a9f6/this-was-a-feature-not-a-bug-mc3</link>
      <guid>https://dev.to/jeet_singh_63644d9175a9f6/this-was-a-feature-not-a-bug-mc3</guid>
      <description>&lt;p&gt;A single ESLint error took me on an unexpected journey into the heart of the React Compiler this week. It was a powerful reminder that there's a deep story behind every rule. Here’s what I learned. 👇&lt;/p&gt;

&lt;p&gt;The Problem&lt;br&gt;
It started with a simple pattern: using an async function inside a useEffect hook. A lint rule flagged my setState call, which I thought was a mistake. Since the state update happened after an await, I was convinced it had to be a false positive.&lt;/p&gt;

&lt;p&gt;The Investigation&lt;br&gt;
My curiosity led me down a rabbit hole. I started by opening an issue on GitHub, but I wanted to understand the root cause. I decided to dive into the React repository myself and trace the logic.&lt;br&gt;
The journey took me from the eslint-plugin-react-compiler wrapper, deep into the babel-plugin-react-compiler, and eventually to the exact file responsible for the logic: src/Validation/ValidateNoSetStateInEffects.ts.&lt;/p&gt;

&lt;p&gt;The "Aha!" Moment 💡&lt;br&gt;
After analyzing the compiler's validation code, I had my 'aha!' moment. The rule isn't a bug; it's a crucial feature designed to prevent memory leaks.&lt;br&gt;
It correctly flags any setState call in the main body of an effect to protect against a classic race condition: the component could unmount while waiting for the await to finish, leading to an attempt to update a non-existent component.&lt;/p&gt;

&lt;p&gt;The Takeaway&lt;br&gt;
My biggest takeaway wasn't just about compilers, but about appreciating the "why" behind the Rules of Hooks. What seems like a simple linting error is often a carefully designed safeguard built on years of experience by the React team.&lt;br&gt;
It was a humbling and incredibly valuable deep dive!&lt;br&gt;
hashtag#ReactJS hashtag#WebDevelopment hashtag#OpenSource hashtag#JavaScript hashtag#LearnInPublic&lt;/p&gt;

</description>
      <category>tooling</category>
      <category>learning</category>
      <category>javascript</category>
      <category>react</category>
    </item>
  </channel>
</rss>
