<?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: Rozeena</title>
    <description>The latest articles on DEV Community by Rozeena (@rossycoder).</description>
    <link>https://dev.to/rossycoder</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%2F4181599%2F51f335d4-28da-4fa6-92f8-846f6316f1df.png</url>
      <title>DEV Community: Rozeena</title>
      <link>https://dev.to/rossycoder</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rossycoder"/>
    <language>en</language>
    <item>
      <title>Graph Hacks build log: I gave my dealership AI a memory for its own alerts</title>
      <dc:creator>Rozeena</dc:creator>
      <pubDate>Thu, 15 Oct 2026 08:54:35 +0000</pubDate>
      <link>https://dev.to/rossycoder/graph-hacks-build-log-i-gave-my-dealership-ai-a-memory-for-its-own-alerts-108i</link>
      <guid>https://dev.to/rossycoder/graph-hacks-build-log-i-gave-my-dealership-ai-a-memory-for-its-own-alerts-108i</guid>
      <description>&lt;p&gt;I keep building Dealership Brain and finding the same embarrassing failure mode: the app nags dealerships about missed callbacks, but had no idea whether its own alerts ever actually went out. Alerts fired into the void. If something failed, nobody knew — including me.&lt;/p&gt;

&lt;p&gt;So today, during the Graph Hacks window, I gave it a memory.&lt;/p&gt;

&lt;p&gt;What's new&lt;/p&gt;

&lt;p&gt;Persistent Alert Log — every n8n alert attempt is now recorded with a status: sent, preview, or failed. Each entry stores what triggered it (usually an overdue callback), when it fired, and the outcome. No more mystery about whether the workflow actually ran.&lt;/p&gt;

&lt;p&gt;Manager Alerts tab — managers get a dedicated tab in the UI showing the alert history. It's the first thing I check now after a busy morning: did the system actually flag everything it should have?&lt;/p&gt;

&lt;p&gt;n8n alert button for overdue callbacks — there's now an explicit trigger that fires the n8n workflow when a callback crosses its SLA deadline. Before this, the overdue check and the alert lived in different places and occasionally disagreed.&lt;/p&gt;

&lt;p&gt;Why this matters&lt;/p&gt;

&lt;p&gt;An AI that reminds humans to follow through on promises needs to be held to the same standard. If the app forgets to send an alert, that's the exact failure it's supposed to prevent. Eating my own dog food, basically.&lt;/p&gt;

&lt;p&gt;The honest state of it: the log is simple, the tab is unstyled, and the failure statuses need better retry handling. But the core loop works — promise missed, alert fired, attempt recorded.&lt;/p&gt;

&lt;p&gt;Try it: &lt;a href="https://dealership-brain.vercel.app" rel="noopener noreferrer"&gt;https://dealership-brain.vercel.app&lt;/a&gt;&lt;br&gt;
Code: &lt;a href="https://github.com/rossycoder/dealership-brain" rel="noopener noreferrer"&gt;https://github.com/rossycoder/dealership-brain&lt;/a&gt;&lt;/p&gt;

</description>
      <category>buildinpublic</category>
      <category>hackathon</category>
      <category>ai</category>
      <category>webdev</category>
    </item>
    <item>
      <title>What Will Your City Feel Like in 2050? I Built a Climate Detective With 40 Years of NASA Data</title>
      <dc:creator>Rozeena</dc:creator>
      <pubDate>Wed, 14 Oct 2026 07:45:35 +0000</pubDate>
      <link>https://dev.to/rossycoder/what-will-your-city-feel-like-in-2050-i-built-a-climate-detective-with-40-years-of-nasa-data-54nd</link>
      <guid>https://dev.to/rossycoder/what-will-your-city-feel-like-in-2050-i-built-a-climate-detective-with-40-years-of-nasa-data-54nd</guid>
      <description>&lt;p&gt;Ask a weather app about climate change and it shows you a chart. Charts don't scare anyone.&lt;/p&gt;

&lt;p&gt;So TerraDetective AI answers differently: your city in 2050 will feel like a city that exists today. Karachi's 2050 climate twin? Riyadh, now. That lands differently — because you've seen Riyadh's heat. You can picture living in it.&lt;/p&gt;

&lt;p&gt;I built TerraDetective for the NASA Space Apps Challenge on 40 years of real NASA POWER data. No projections invented by a language model — measured data, analyzed live.&lt;/p&gt;

&lt;p&gt;The feature to try first: Future Twin City. Pick your city; the tool analyzes its temperature trajectory and finds its 2050 climate twin among real cities today.&lt;/p&gt;

&lt;p&gt;Also inside:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Was This Normal? — pick any month in history, get a z-score verdict: normal, unusual, or off the charts&lt;/li&gt;
&lt;li&gt;Danger Days — count of days per year above heat thresholds, trended over decades&lt;/li&gt;
&lt;li&gt;Real statistics — every trend ships with a 95% confidence interval and a p-value. If the trend isn't significant, the tool says so.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last point is the whole philosophy: a climate tool that overstates its case is just propaganda with better charts. Every number carries its uncertainty.&lt;/p&gt;

&lt;p&gt;Run your city through it:&lt;br&gt;
👉 &lt;a href="https://terradetective-ai.vercel.app" rel="noopener noreferrer"&gt;https://terradetective-ai.vercel.app&lt;/a&gt;&lt;br&gt;
Code: &lt;a href="https://github.com/rossycoder/terradetective-ai" rel="noopener noreferrer"&gt;https://github.com/rossycoder/terradetective-ai&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Built for NASA Space Apps. Tell me your city's 2050 twin in the comments — the surprising ones are the best argument for building tools like this.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>data</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Smog Season Is Coming — I Built a Free Tool That Tells Parents If Kids Should Go to School</title>
      <dc:creator>Rozeena</dc:creator>
      <pubDate>Wed, 14 Oct 2026 05:57:20 +0000</pubDate>
      <link>https://dev.to/rossycoder/smog-season-is-coming-i-built-a-free-tool-that-tells-parents-if-kids-should-go-to-school-1n0h</link>
      <guid>https://dev.to/rossycoder/smog-season-is-coming-i-built-a-free-tool-that-tells-parents-if-kids-should-go-to-school-1n0h</guid>
      <description>&lt;p&gt;In Lahore and Delhi, winter smog season means the same morning question in millions of homes: is it safe to send the kids to school today?&lt;/p&gt;

&lt;p&gt;AQI apps answer with a number. Numbers don't make decisions — parents do, at 7am, half-awake. I built HawaGuard for the Code for a Billion hackathon to turn air-quality data into decisions.&lt;/p&gt;

&lt;p&gt;🛡️ Start with Family Shield: enter your child's age and any respiratory sensitivity, get a plain school-day verdict — go, go with a mask, or keep home if you can — with the reason stated, not just a color.&lt;/p&gt;

&lt;p&gt;Also built in:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Outdoor Planner — for walkers and the elderly: not just "AQI now," but the best hour today to go out&lt;/li&gt;
&lt;li&gt;Symptom Checker — is this cough pollution irritation or an infection worth a clinic visit? (Guidance, not diagnosis — it says so in the app.)&lt;/li&gt;
&lt;li&gt;Roman Urdu mode — full guidance in the language people actually speak at home&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Decisions need local data homeowners trust, so HawaGuard uses labeled monitoring stations. A note on honesty: one station series in the demo is Beijing historical data, clearly labeled — because PM2.5 health physics is the same everywhere, and pretending it's local when it isn't would break the whole point of the app.&lt;/p&gt;

&lt;p&gt;Check today's verdict for your city:&lt;br&gt;
👉 &lt;a href="https://hawaguard.vercel.app" rel="noopener noreferrer"&gt;https://hawaguard.vercel.app&lt;/a&gt;&lt;br&gt;
Code: &lt;a href="https://github.com/rossycoder/hawaguard" rel="noopener noreferrer"&gt;https://github.com/rossycoder/hawaguard&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Parents — what do you actually check before school on a smog day? Building the next version from your answers.&lt;/p&gt;

&lt;h1&gt;
  
  
  CodeForABillion #PublicHealth #AirQuality #Smog #Hackathon #buildinpublic
&lt;/h1&gt;

</description>
      <category>javascript</category>
      <category>api</category>
      <category>webdev</category>
      <category>datascience</category>
    </item>
    <item>
      <title>I Built a Free Tool That Shows Small Shops Exactly How Much Cash Is Trapped in Dead Stock</title>
      <dc:creator>Rozeena</dc:creator>
      <pubDate>Wed, 14 Oct 2026 05:56:54 +0000</pubDate>
      <link>https://dev.to/rossycoder/i-built-a-free-tool-that-shows-small-shops-exactly-how-much-cash-is-trapped-in-dead-stock-1gnb</link>
      <guid>https://dev.to/rossycoder/i-built-a-free-tool-that-shows-small-shops-exactly-how-much-cash-is-trapped-in-dead-stock-1gnb</guid>
      <description>&lt;p&gt;A small shop owner I know had thousands of dollars of stock sitting on shelves that hadn't moved in months. Still paying rent on that shelf space. Still reordering the things that DID sell — by gut feel.&lt;/p&gt;

&lt;p&gt;Retail doesn't have a data problem. It has a trapped-cash problem. I built StockSentry for the InfiniSynapse Vibe Coding Hackathon to put a number on it — free, no signup, works from a CSV export your POS already makes.&lt;/p&gt;

&lt;p&gt;Start here: the Dead Stock Detector. Upload your inventory and it tells you exactly how much cash is locked in SKUs that haven't sold in 30/60/90 days. Not a chart. A number, in dollars, per item.&lt;/p&gt;

&lt;p&gt;Then:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Discount Ladder Simulator — if you discount 10/20/30%, how long until it clears? What do you recover vs. write off?&lt;/li&gt;
&lt;li&gt;Viral Spike Simulator — a product goes viral overnight. What breaks first? What do you lose by stocking out on day two?&lt;/li&gt;
&lt;li&gt;True Restock Calculator — reorder points from actual velocity, not habit&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One promise on the tin: StockSentry labels every number honestly. If a figure comes from a heuristic, it says so. If it's AI-assisted analysis, it's badged as such. Black-box "AI says so" is how tools lose trust with real shop owners.&lt;/p&gt;

&lt;p&gt;Try it with the built-in demo CSV:&lt;br&gt;
👉 &lt;a href="https://stocksentry-bice.vercel.app" rel="noopener noreferrer"&gt;https://stocksentry-bice.vercel.app&lt;/a&gt;&lt;br&gt;
Code: &lt;a href="https://github.com/rossycoder/stocksentry" rel="noopener noreferrer"&gt;https://github.com/rossycoder/stocksentry&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Shop owners and retail folks: what's your dead-stock number? I genuinely want to know if the detector matches what you see on your shelves.&lt;/p&gt;

&lt;h1&gt;
  
  
  smallbusiness #retail #inventory #ai #hackathon #buildinpublic
&lt;/h1&gt;

</description>
      <category>python</category>
      <category>fastapi</category>
      <category>ai</category>
      <category>webdev</category>
    </item>
    <item>
      <title>I Built an AI "Brain" for Car Dealerships That Never Forgets a Customer</title>
      <dc:creator>Rozeena</dc:creator>
      <pubDate>Tue, 13 Oct 2026 08:20:17 +0000</pubDate>
      <link>https://dev.to/rossycoder/i-built-an-ai-brain-for-car-dealerships-that-never-forgets-a-customer-36ch</link>
      <guid>https://dev.to/rossycoder/i-built-an-ai-brain-for-car-dealerships-that-never-forgets-a-customer-36ch</guid>
      <description>&lt;p&gt;A customer calls a dealership and is promised a callback in 15 minutes. Nobody calls back. They buy from a competitor.&lt;/p&gt;

&lt;p&gt;This isn't a sales problem — it's a memory problem. Salespeople forget. CRMs don't remind. So I built Dealership Brain for the FalkorDB Graph Hacks hackathon: an AI operations brain that stores every customer, every promise, and every conversation in a knowledge graph — and escalates before a broken promise costs a sale.&lt;/p&gt;

&lt;p&gt;🔴 The feature that matters most: Callback SLA Escalation. Every callback promise gets a timer. Miss it, and the case automatically escalates to the manager. No customer silently falls through the cracks again.&lt;/p&gt;

&lt;p&gt;Also inside:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Promise Tracker — every commitment made to a customer, tracked to done&lt;/li&gt;
&lt;li&gt;Smart Match — a new car arrives, the brain finds buyers who wanted exactly that, and drafts the WhatsApp message&lt;/li&gt;
&lt;li&gt;Follow-Up Agent — surfaces who to contact today and why&lt;/li&gt;
&lt;li&gt;Trade-In Valuation — trade-in value + remaining loan → net equity&lt;/li&gt;
&lt;li&gt;Test Drive Booking — double-booking is rejected outright&lt;/li&gt;
&lt;li&gt;Neighborhood Graph — customers visualized as a connected network&lt;/li&gt;
&lt;li&gt;Roman Urdu chat — because that's how many customers actually write&lt;/li&gt;
&lt;li&gt;Staff Leaderboard + service reminders&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;How it works: a FastAPI backend over a graph store. Every interaction becomes nodes and edges, so the system reasons about relationships, not rows. Ask "which customers were promised a callback this week and never got one?" — a graph answers that natively. A traditional CRM makes you dig.&lt;/p&gt;

&lt;p&gt;Try it — simulate a missed callback and watch the escalation fire:&lt;br&gt;
👉 &lt;a href="https://dealership-brain.vercel.app" rel="noopener noreferrer"&gt;https://dealership-brain.vercel.app&lt;/a&gt;&lt;br&gt;
Code: &lt;a href="https://github.com/rossycoder/dealership-brain" rel="noopener noreferrer"&gt;https://github.com/rossycoder/dealership-brain&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Built for FalkorDB Graph Hacks. Feedback welcome — especially from anyone who's worked a dealership floor: what's the promise your team breaks most?&lt;/p&gt;

&lt;h1&gt;
  
  
  buildinpublic #ai #hackathon #python #webdev
&lt;/h1&gt;

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