<?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: Vishwanath Barve</title>
    <description>The latest articles on DEV Community by Vishwanath Barve (@coderoggy).</description>
    <link>https://dev.to/coderoggy</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%2F4159796%2Ff0a7194a-3895-4f36-bc2d-c1c712931e15.jpg</url>
      <title>DEV Community: Vishwanath Barve</title>
      <link>https://dev.to/coderoggy</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/coderoggy"/>
    <language>en</language>
    <item>
      <title>PaperCuts — Turn confusing documents into verified actions</title>
      <dc:creator>Vishwanath Barve</dc:creator>
      <pubDate>Mon, 26 Oct 2026 19:29:25 +0000</pubDate>
      <link>https://dev.to/coderoggy/papercuts-turn-confusing-documents-into-verified-actions-3nl2</link>
      <guid>https://dev.to/coderoggy/papercuts-turn-confusing-documents-into-verified-actions-3nl2</guid>
      <description>&lt;p&gt;PaperCuts is an AI-powered document intelligence platform that helps people understand complicated documents and figure out exactly what they need to do next.&lt;/p&gt;

&lt;p&gt;The idea is simple: people receive important documents containing eligibility rules, deadlines, conditions, required documents, exceptions, and instructions. These details are often scattered across dozens of pages, buried in formal language, or difficult to interpret correctly.&lt;/p&gt;

&lt;p&gt;PaperCuts turns those documents into traceable facts, personalized checklists, deadlines, and actionable next steps—while showing the original evidence behind every important conclusion.&lt;/p&gt;

&lt;p&gt;Demo - &lt;a href="https://coderoggy78.github.io/PaperCuts/" rel="noopener noreferrer"&gt;https://coderoggy78.github.io/PaperCuts/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
    </item>
    <item>
      <title>R I F T - Local-First AI Agent Incident Investigation &amp; Observability Platform</title>
      <dc:creator>Vishwanath Barve</dc:creator>
      <pubDate>Thu, 22 Oct 2026 17:12:47 +0000</pubDate>
      <link>https://dev.to/coderoggy/r-i-f-t-local-first-ai-agent-incident-investigation-observability-platform-1nlg</link>
      <guid>https://dev.to/coderoggy/r-i-f-t-local-first-ai-agent-incident-investigation-observability-platform-1nlg</guid>
      <description>&lt;p&gt;RIFT is a local-first, forensic incident investigation and observability platform engineered specifically for autonomous AI software agents.&lt;/p&gt;

&lt;p&gt;When modern AI coding agents (Devin, Claude Code, Cursor Composer, AutoGPT, SWE-agent) interact with filesystems, terminals, databases, and developer tools, their failures rarely resemble traditional software exceptions. Agents can delete vital source files while assuming they are temporary artifacts, enter infinite retry loops, hallucinate success despite failing builds, or silently trigger catastrophic regressions across downstream codebases.&lt;/p&gt;

&lt;p&gt;RIFT bridges the gap between agent intent and runtime reality through a unified engineering pipeline:&lt;/p&gt;

&lt;p&gt;High-Density Execution Graph &amp;amp; Timeline: Reconstructs execution traces into an interactive Directed Acyclic Graph (DAG) with tri-directional synchronized inspection.&lt;/p&gt;

&lt;p&gt;Deterministic Incident Detection: High-speed, rule-based detector (8 core rules) operating with 0% false positives and zero LLM hallucination risk.&lt;/p&gt;

&lt;p&gt;Google Gemma Forensic Investigation: Local-first inference using Google Gemma models via Ollama to generate multi-hypothesis causal post-mortem with 100% verified trace citations.&lt;/p&gt;

&lt;p&gt;AST Codebase Knowledge &amp;amp; Blast Radius (Graphify): Extracts code syntax trees and call hierarchies with zero external API costs to map the exact blast radius of destructive agent actions.&lt;/p&gt;

&lt;p&gt;Counterfactual Replay Lab: Containerized, dual-isolated sandbox executing typed filesystem mutations to reproduce failures and cryptographically verify developer fixes.&lt;/p&gt;

&lt;p&gt;Executive Incident Post-Mortems: Single-click export of engineering post-mortems in GitHub-Flavored Markdown and machine-readable JSON.&lt;/p&gt;

&lt;p&gt;Check the codebase here - &lt;a href="https://github.com/CoderOggy78/RIFT/tree/main" rel="noopener noreferrer"&gt;https://github.com/CoderOggy78/RIFT/tree/main&lt;/a&gt;&lt;/p&gt;

</description>
      <category>hf26challenge</category>
    </item>
    <item>
      <title>I Built WRID : An AI-Powered Research Internship Workspace for Students</title>
      <dc:creator>Vishwanath Barve</dc:creator>
      <pubDate>Sun, 18 Oct 2026 16:10:54 +0000</pubDate>
      <link>https://dev.to/coderoggy/i-built-wrid-an-ai-powered-research-internship-workspace-for-students-528i</link>
      <guid>https://dev.to/coderoggy/i-built-wrid-an-ai-powered-research-internship-workspace-for-students-528i</guid>
      <description>&lt;p&gt;This is a submission for the Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle.&lt;/p&gt;

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

&lt;p&gt;Finding a research internship is harder than it should be.&lt;/p&gt;

&lt;p&gt;When I started exploring research opportunities, I realized how much time students spend searching faculty websites, finding relevant professors, reading papers, writing cold emails, and tracking applications.&lt;/p&gt;

&lt;p&gt;Most students end up with dozens of browser tabs, messy spreadsheets, and generic email templates.&lt;/p&gt;

&lt;p&gt;So I built WRID (Winter Research Internship Desk) — a workspace that brings the entire research internship process into one place.&lt;/p&gt;

&lt;p&gt;Here's what it does:&lt;/p&gt;

&lt;p&gt;Faculty Directory: Search 1,610+ professors across 49 institutions, with filters for departments and research interests.&lt;/p&gt;

&lt;p&gt;AI Resume Matching: Upload your resume and find professors whose research aligns with your skills and projects.&lt;/p&gt;

&lt;p&gt;Academic Email Studio: Use Gemma and Llama to draft, personalize, and review research outreach emails.&lt;/p&gt;

&lt;p&gt;Fellowship Discovery: Explore research programs at institutions such as IITs, MIT, ETH Zürich, and CERN.&lt;/p&gt;

&lt;p&gt;Application Tracker: Manage applications, follow-ups, and progress without maintaining separate spreadsheets.&lt;/p&gt;

&lt;p&gt;Research Roadmap: A structured six-week plan to prepare for research internships.&lt;/p&gt;

&lt;p&gt;The idea is simple: spend less time figuring out whom to contact and more time doing actual research.&lt;/p&gt;

&lt;p&gt;Who Would Pay for It?&lt;/p&gt;

&lt;p&gt;Students applying for competitive research internships are the primary users. A potential paid tier could offer advanced faculty matching, deeper research analysis, and additional AI-assisted outreach features.&lt;/p&gt;

&lt;p&gt;The core discovery tools should remain accessible.&lt;/p&gt;

&lt;p&gt;Demo&lt;/p&gt;

&lt;p&gt;Live Website:(&lt;a href="https://hacktoberfest-winter-research.vercel.app" rel="noopener noreferrer"&gt;https://hacktoberfest-winter-research.vercel.app&lt;/a&gt;)&lt;/p&gt;

&lt;p&gt;Code&lt;/p&gt;

&lt;p&gt;GitHub:(&lt;a href="https://github.com/CoderOggy78/WRID" rel="noopener noreferrer"&gt;https://github.com/CoderOggy78/WRID&lt;/a&gt;)&lt;/p&gt;

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

&lt;p&gt;WRID uses React 19, TypeScript, Vite, and Tailwind CSS for the frontend.&lt;/p&gt;

&lt;p&gt;For AI, I integrated Google Gemma and Meta Llama 3.3 70B through Groq into the academic writing workflow.&lt;/p&gt;

&lt;p&gt;The system combines two approaches:&lt;/p&gt;

&lt;p&gt;Rule-based matching: Extracts skills, projects, and research interests from resumes and compares them against faculty research profiles. The resulting scores indicate estimated alignment, not acceptance chances.&lt;/p&gt;

&lt;p&gt;Open-weight LLMs: Help students refine cold emails, improve academic tone, and prepare personalized follow-ups.&lt;/p&gt;

&lt;p&gt;Resume text extraction and application tracking run client-side, with application data stored in the browser. AI requests using hosted providers are processed through their respective APIs.&lt;/p&gt;

&lt;p&gt;The biggest challenge was making the recommendations useful rather than simply displaying a list of professors with arbitrary scores.&lt;/p&gt;

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

&lt;p&gt;I didn't want WRID's AI features to depend entirely on one proprietary model.&lt;/p&gt;

&lt;p&gt;Using open-weight models like Gemma and Llama gives me the flexibility to experiment with different models, compare their performance, and potentially support local inference in the future.&lt;/p&gt;

&lt;p&gt;That matters for a student-focused product where cost, accessibility, and privacy are important.&lt;/p&gt;

&lt;p&gt;It also means the AI layer can evolve without rebuilding the entire application.&lt;/p&gt;

&lt;p&gt;The goal isn't to add AI everywhere. It's to use it where it genuinely reduces the work students have to do.&lt;/p&gt;

&lt;p&gt;Prize Categories&lt;/p&gt;

&lt;p&gt;Side Hustle — Open-Source AI Challenge, Week 2&lt;/p&gt;

&lt;p&gt;WRID is still evolving, and there's plenty I want to improve, particularly research matching, faculty data quality, and fellowship discovery.&lt;/p&gt;

&lt;p&gt;If you're a student applying for research internships, I'd genuinely appreciate you trying it.&lt;/p&gt;

&lt;p&gt;What part of the research internship application process do you find most frustrating?&lt;/p&gt;

&lt;p&gt;I'd love to use that feedback to decide what to build next.&lt;/p&gt;

&lt;h1&gt;
  
  
  Hacktoberfest #OpenSourceAI #Gemma #Llama #React #ResearchInternships
&lt;/h1&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
    </item>
  </channel>
</rss>
