<?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: Nency Chandiramani</title>
    <description>The latest articles on DEV Community by Nency Chandiramani (@nency_chandiramani).</description>
    <link>https://dev.to/nency_chandiramani</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%2F4153657%2F85cb863e-cce1-4b00-b573-477f380efbe0.png</url>
      <title>DEV Community: Nency Chandiramani</title>
      <link>https://dev.to/nency_chandiramani</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nency_chandiramani"/>
    <language>en</language>
    <item>
      <title>Footsteps: What If Your Audio Story Could Only Move When You Do?</title>
      <dc:creator>Nency Chandiramani</dc:creator>
      <pubDate>Sun, 11 Oct 2026 05:58:32 +0000</pubDate>
      <link>https://dev.to/nency_chandiramani/footsteps-what-if-your-audio-story-could-only-move-when-you-do-oo9</link>
      <guid>https://dev.to/nency_chandiramani/footsteps-what-if-your-audio-story-could-only-move-when-you-do-oo9</guid>
      <description>&lt;p&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;/p&gt;

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

&lt;p&gt;What if your next audio thriller could only move forward when you did?&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Footsteps&lt;/strong&gt; is an experimental, location-aware audio mystery that turns an ordinary walk into an interactive story. Instead of staring at a screen to progress through a game, you put your phone in your pocket, wear your earbuds, and step outside.&lt;/p&gt;

&lt;p&gt;The idea is simple: the world around you becomes part of the narrative.&lt;/p&gt;

&lt;p&gt;Footsteps uses real nearby landmarks to ground its story in your surroundings. As you walk or jog, the story adapts to your pace, creating a mystery that unfolds along your route. The goal is to make movement part of the experience rather than another activity tracked on a screen.&lt;/p&gt;

&lt;p&gt;It's designed for people who enjoy immersive storytelling but spend too much time looking at their devices. Your neighborhood becomes the setting, your movement becomes the trigger, and the next chapter is something you experience rather than watch.&lt;/p&gt;

&lt;p&gt;The central principle is that &lt;strong&gt;the story should respond to the real world, not invent one.&lt;/strong&gt;&lt;/p&gt;

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

&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%2Fju5rsnoovebioktl79ki.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%2Fju5rsnoovebioktl79ki.png" alt=" " width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The project is organized around a lightweight FastAPI backend and a mobile-first Progressive Web App. The backend handles location processing, pace detection, landmark selection, story generation, and session data. The frontend handles GPS updates, audio playback, and the session recap.&lt;/p&gt;

&lt;p&gt;The code is designed to keep location geometry and story generation separate, making the system easier to test and the model easier to replace.&lt;/p&gt;

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

&lt;p&gt;Footsteps combines conventional programming with open-source AI. Each component has a specific responsibility.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Gemma through Ollama:&lt;/strong&gt; Generates short mystery narration from structured session data.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;OpenStreetMap and Overpass API:&lt;/strong&gt; Supplies real nearby landmarks without requiring a paid maps API.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Python and FastAPI:&lt;/strong&gt; Handle GPS pings, pace detection, geometry, story state, and backend endpoints.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Piper / browser speech synthesis:&lt;/strong&gt; Provides spoken narration, with browser speech synthesis as the fallback when server-side audio is unavailable.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tiger Data / TimescaleDB:&lt;/strong&gt; Provides time-series storage for movement points and story beats, with SQL-based session summaries.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sentry:&lt;/strong&gt; Provides tracing and debugging visibility across the story-generation pipeline.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Render:&lt;/strong&gt; Hosts the web application and backend.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One architectural decision matters more than the number of technologies involved: &lt;strong&gt;code finds the facts; the language model writes the words.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The backend calculates distances and bearings, filters nearby landmarks, and constructs a structured state object. Gemma receives that data and writes the next beat. Its response must pass validation before narration, with a retry and deterministic fallback for invalid output.&lt;/p&gt;

&lt;p&gt;This separation makes the experience more grounded and gives the application explicit control over safety rules.&lt;/p&gt;

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

&lt;p&gt;Footsteps uses location and movement data to create a personal experience. That makes openness and control important design considerations, not just technology preferences.&lt;/p&gt;

&lt;p&gt;Open-weight models make it possible to run inference on infrastructure I control rather than making a closed, hosted language model the central dependency. Ollama also makes the model configurable, so a compatible model can be changed through an environment variable.&lt;/p&gt;

&lt;p&gt;OpenStreetMap provides a community-maintained source of real-world geographic data. Open-source speech tools offer another route to narration without requiring a proprietary voice-generation API.&lt;/p&gt;

&lt;p&gt;Open infrastructure also makes the project easier to inspect, adapt, and extend. Developers can examine how landmarks are selected, how directions are calculated, how model output is validated, and how movement metrics are derived.&lt;/p&gt;

&lt;p&gt;My goal is to keep the application transparent about what it knows, what the model generates, and what happens when a component fails.&lt;/p&gt;

&lt;p&gt;Location privacy and safety remain essential: stored coordinates should be coarsened, sessions should be deletable, and narration must never encourage dangerous movement or pressure someone to continue exercising.&lt;/p&gt;

&lt;h2&gt;
  
  
  My Agent Session
&lt;/h2&gt;

&lt;p&gt;[Optional: Add your DevRelay agent-session link or embed your saved session here.]&lt;/p&gt;

&lt;p&gt;I used an AI coding agent to accelerate implementation and help assemble the project under hackathon time constraints. The engineering challenge is not simply generating code; it is verifying that the individual components work together and that the resulting experience behaves reliably outside a development environment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Gemma:&lt;/strong&gt; Open-weight language model for grounded story generation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tiger Data:&lt;/strong&gt; Time-series persistence and movement analytics.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sentry:&lt;/strong&gt; Agent tracing across the narration pipeline.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Render:&lt;/strong&gt; Application hosting and deployment.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
    </item>
    <item>
      <title>"I KNOW I Saved This Somewhere": I Built MEMORY for My Best Friend Ritika</title>
      <dc:creator>Nency Chandiramani</dc:creator>
      <pubDate>Mon, 05 Oct 2026 06:52:04 +0000</pubDate>
      <link>https://dev.to/nency_chandiramani/i-know-i-saved-this-somewhere-i-built-memory-for-my-best-friend-ritika-3kj9</link>
      <guid>https://dev.to/nency_chandiramani/i-know-i-saved-this-somewhere-i-built-memory-for-my-best-friend-ritika-3kj9</guid>
      <description>&lt;p&gt;&lt;em&gt;This is my submission for the Hacktoberfest Weekend Challenge: Build for a Friend.&lt;/em&gt;&lt;/p&gt;

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

&lt;p&gt;My best friend Ritika is preparing for CA, and she saves everything.&lt;/p&gt;

&lt;p&gt;Screenshots of study roadmaps. PDFs of notes. Messages with useful links. A resource someone recommended once, a tip she might need in six months, a random fact that could matter someday. If something might be useful later, Ritika saves it.&lt;/p&gt;

&lt;p&gt;I love this about her. She's thoughtful and always thinking a few steps ahead.&lt;/p&gt;

&lt;p&gt;But over time, "everything" turned into thousands of screenshots and files. And the problem was never saving things. The problem was finding them again.&lt;/p&gt;

&lt;p&gt;Her phone and laptop are full of files named things like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;IMG_83921.png
Screenshot_2026_10_02.png
final_notes_2.pdf
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;One day she said, half joking:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"I wish there was something where I could just describe what I remember and it would find the screenshot for me."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That sentence stuck with me. She doesn't want a better folder system. She wants to say what she remembers and have the thing show up.&lt;/p&gt;

&lt;p&gt;So I built &lt;strong&gt;MEMORY&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;MEMORY is a privacy-first, local-first personal memory system. With it you can:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Explicitly remember web pages&lt;/strong&gt; through a Chrome extension&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Index and search files on your own computer&lt;/strong&gt;: PDFs, DOCX, TXT, Markdown, CSV, and images/screenshots&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Search in natural language&lt;/strong&gt; instead of guessing filenames&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Instead of searching for &lt;code&gt;Screenshot_2026_10_02.png&lt;/code&gt;, you ask:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Find the screenshot about the Java internship that mentioned Spring Boot."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;And MEMORY finds it.&lt;/p&gt;

&lt;p&gt;Somewhere along the way I realized something simple:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;People don't think in filenames. They think in memories.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;You don't remember that the file was called &lt;code&gt;IMG_83921.png&lt;/code&gt;. You remember what it was about.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;You don't need to remember the file. You only need to remember what you remember about it.&lt;/strong&gt;&lt;/p&gt;

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

&lt;p&gt;🌐 *&lt;em&gt;Live video link : *&lt;/em&gt; &lt;a href="https://youtu.be/m_iiqkLiJco" rel="noopener noreferrer"&gt;https://youtu.be/m_iiqkLiJco&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🌐 &lt;strong&gt;Live demo:&lt;/strong&gt; &lt;a href="https://memory-ai-zkxv.onrender.com/" rel="noopener noreferrer"&gt;https://memory-ai-zkxv.onrender.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;💻 &lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/nencycodes/memory-ai" rel="noopener noreferrer"&gt;nencycodes/memory-ai&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The video shows:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The MEMORY browser extension&lt;/li&gt;
&lt;li&gt;Searching for the Java internship / Spring Boot screenshot&lt;/li&gt;
&lt;li&gt;The correct screenshot being retrieved and opened&lt;/li&gt;
&lt;li&gt;A second, completely unrelated image being searched and retrieved by its content&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A quick honesty note about the live demo: the Render deployment is a public demo of the app. A hosted server can't reach into anyone's personal files, and it shouldn't be able to. The full local-first experience, indexing files on your own machine, runs on your own computer.&lt;/p&gt;

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

&lt;p&gt;Here's the shape of the system:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Chrome Extension  ─┐
                   ├─► FastAPI backend ─► local memory index ─► semantic search
Local files       ─┘
(PDF, DOCX, TXT, MD, CSV, images)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;The stack:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Chrome Extension&lt;/li&gt;
&lt;li&gt;Python + FastAPI&lt;/li&gt;
&lt;li&gt;Gemma API (for explicit image understanding)&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;sentence-transformers&lt;/code&gt; with &lt;code&gt;all-MiniLM-L6-v2&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Local semantic search&lt;/li&gt;
&lt;li&gt;GitHub Copilot coding agent&lt;/li&gt;
&lt;li&gt;Render for the public demo deployment&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The interesting part: screenshots
&lt;/h3&gt;

&lt;p&gt;Text files are the easier case. The hard part is images, because a screenshot is just pixels until something reads it. This is the pipeline:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Image
  → Gemma image understanding
  → OCR + useful visual/contextual description
  → searchable representation
  → all-MiniLM-L6-v2 embedding
  → local memory index
  → semantic search
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;When you explicitly choose to index an image, Gemini reads it and produces the text in it plus a useful description of what it shows. That becomes the image's searchable representation. I then embed it locally with &lt;code&gt;all-MiniLM-L6-v2&lt;/code&gt; and store it in the local index.&lt;/p&gt;

&lt;p&gt;One detail matters for both cost and privacy: &lt;strong&gt;Gemini is only called during explicit image indexing, not on every search.&lt;/strong&gt; When you search, your query is embedded locally and matched against the local index.&lt;/p&gt;

&lt;h3&gt;
  
  
  Testing it
&lt;/h3&gt;

&lt;p&gt;I tested with two screenshots:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A Java / Spring Boot screenshot&lt;/li&gt;
&lt;li&gt;A completely unrelated cloud screenshot&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I wanted to know whether MEMORY understood the &lt;em&gt;content&lt;/em&gt; of images or whether it only worked on my first example. The unrelated screenshot was also retrieved by its content, not just its filename.&lt;/p&gt;

&lt;p&gt;That's a small test, not a benchmark, and I'm not going to dress it up with numbers I don't have. Nothing in the system is trained or tuned for Java. The pipeline is general: whatever Gemini can read and describe becomes searchable.&lt;/p&gt;

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

&lt;p&gt;Think about what a personal memory system holds: screenshots of private conversations, study material, documents, things you saved because they mattered to you. For many people it's the most personal dataset they own.&lt;/p&gt;

&lt;p&gt;My rule while building MEMORY was:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Your data belongs to you. AI should come to the data; your data should not automatically go to AI.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Open and local components make that practical. Because the embedding model (&lt;code&gt;all-MiniLM-L6-v2&lt;/code&gt;) is open and small enough to run on a normal machine, the retrieval layer doesn't need your whole archive sitting in a cloud search system. Search happens on your device.&lt;/p&gt;

&lt;p&gt;I want to be precise here: &lt;strong&gt;MEMORY is not 100% local.&lt;/strong&gt; Gemini is used for image understanding when you explicitly index an image, so that image's content goes to the Gemini API at that moment. What &lt;em&gt;is&lt;/em&gt; local is the semantic retrieval, the embedding layer, and the index itself.&lt;/p&gt;

&lt;p&gt;MEMORY is designed around:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Explicit user actions.&lt;/strong&gt; Nothing is remembered unless you choose to remember it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No silent browsing-history collection.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No automatic folder surveillance.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Local semantic retrieval.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;User control&lt;/strong&gt; over what gets indexed.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Not every useful AI system has to start with "upload everything." When the building blocks are open and small enough to run locally, the privacy-friendly design becomes the easy one, and a solo developer can build it.&lt;/p&gt;

&lt;h2&gt;
  
  
  My Agent Session
&lt;/h2&gt;

&lt;p&gt;I used &lt;strong&gt;GitHub Copilot's coding agent&lt;/strong&gt; as a collaborator throughout the build. It helped with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The &lt;strong&gt;FastAPI backend&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;The &lt;strong&gt;image indexing pipeline&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Semantic search integration&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Debugging and testing&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deployment work&lt;/strong&gt; for the Render demo&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I still made the product decisions: what MEMORY should and shouldn't do, where the privacy lines are, and how honest to be about what runs where. The agent helped me move faster on the implementation.&lt;/p&gt;

&lt;p&gt;🔗 &lt;strong&gt;Agent session link (optional):&lt;/strong&gt; [AGENT SESSION LINK]&lt;/p&gt;

&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Best Use of Gemma
&lt;/h3&gt;

&lt;p&gt;MEMORY uses Google's open-weight Gemma model as part of its AI-powered memory pipeline.&lt;/p&gt;

&lt;p&gt;Gemma is used to understand and process the information that becomes part of a user's searchable memory, helping turn raw saved content into a representation that can be retrieved using natural-language queries.&lt;/p&gt;

&lt;h3&gt;
  
  
  Best Use of GitHub Copilot
&lt;/h3&gt;

&lt;p&gt;I used GitHub Copilot's coding agent throughout development to build and iterate on the FastAPI backend, image-indexing pipeline, semantic search, testing, debugging, and deployment workflow.&lt;/p&gt;

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

&lt;p&gt;&lt;strong&gt;Search is really about how people remember.&lt;/strong&gt; I started out thinking about indexing files. I ended up thinking about how people recall things: by content, by context, by "the one that mentioned that internship." Building for Ritika made me design around how she actually thinks, not how file systems are organized.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Privacy decisions are architecture decisions.&lt;/strong&gt; "Explicit indexing only" and "no background crawling" aren't settings you add at the end. They shape the whole design.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Being honest about the boundary builds more trust than a big claim.&lt;/strong&gt; Writing "this part is local, this part isn't" felt less impressive at first, but it's the version I'd want to read as a user.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A small, real test beats a big, vague claim.&lt;/strong&gt; Retrieving an unrelated screenshot by its content told me more about the pipeline than any amount of hand-waving.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's Next?
&lt;/h2&gt;

&lt;p&gt;MEMORY is a prototype, and there's a lot I want to do:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Make &lt;strong&gt;setup and local indexing smoother&lt;/strong&gt; for non-developers (Ritika should be able to use this without me)&lt;/li&gt;
&lt;li&gt;Add &lt;strong&gt;more careful evaluation&lt;/strong&gt; of retrieval quality on larger, messier collections&lt;/li&gt;
&lt;li&gt;Explore &lt;strong&gt;fully local image understanding&lt;/strong&gt;, to shrink the part that depends on an external API&lt;/li&gt;
&lt;li&gt;Improve the &lt;strong&gt;search experience&lt;/strong&gt;: filters, previews, and better ways to refine "no, not that one"&lt;/li&gt;
&lt;li&gt;Keep every new feature behind the same rule: explicit, local-first, user-controlled&lt;/li&gt;
&lt;/ul&gt;

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

&lt;p&gt;I didn't want to build another chatbot.&lt;/p&gt;

&lt;p&gt;There are already plenty of those. What I kept coming back to was something much smaller and much more human, a sentence almost everyone has said at some point:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"I remember saving this somewhere. Can you find it?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It started with Ritika's offhand wish and a pile of files named &lt;code&gt;IMG_83921.png&lt;/code&gt;. It became a small tool that lets you search by what you remember instead of what you named things.&lt;/p&gt;

&lt;p&gt;I'm still early, and there's a long way to go. But if one person never has to scroll through thousands of screenshots again, it was worth building.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Built for Ritika. Built for everyone who has ever said:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;"I KNOW I saved this somewhere."&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>weekendchallenge</category>
      <category>hf26challenge</category>
    </item>
    <item>
      <title>Hello DEV! 👋 This Is My First Post</title>
      <dc:creator>Nency Chandiramani</dc:creator>
      <pubDate>Fri, 02 Oct 2026 11:30:26 +0000</pubDate>
      <link>https://dev.to/nency_chandiramani/hello-dev-this-is-my-first-post-388n</link>
      <guid>https://dev.to/nency_chandiramani/hello-dev-this-is-my-first-post-388n</guid>
      <description>&lt;p&gt;Hey everyone! 👋&lt;/p&gt;

&lt;p&gt;This is officially my first post on DEV.to!&lt;/p&gt;

&lt;p&gt;I recently discovered the amazing world of open source and decided to participate in Hacktoberfest this year. 🌱&lt;/p&gt;

&lt;p&gt;I'm still figuring things out, learning how GitHub, repositories, issues, and pull requests work, and honestly... I'm excited to see where this takes me.&lt;/p&gt;

&lt;p&gt;I'm hoping to learn, contribute, make some mistakes, and hopefully make a few meaningful contributions along the way.&lt;/p&gt;

&lt;p&gt;So... hello DEV community! 👋&lt;/p&gt;

&lt;p&gt;Day 1 starts here. 🚀&lt;/p&gt;

&lt;p&gt;Let's see where this journey goes!&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>github</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
