<?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: Adnan Ahmed</title>
    <description>The latest articles on DEV Community by Adnan Ahmed (@adnanahmed818).</description>
    <link>https://dev.to/adnanahmed818</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%2F4156571%2Fcff058b5-9de7-45d6-9904-6f3089cb3b8d.png</url>
      <title>DEV Community: Adnan Ahmed</title>
      <link>https://dev.to/adnanahmed818</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/adnanahmed818"/>
    <language>en</language>
    <item>
      <title>👻 The Haunted Terminal: When Your Shell Gets Possessed by Open-Source AI</title>
      <dc:creator>Adnan Ahmed</dc:creator>
      <pubDate>Thu, 29 Oct 2026 06:35:14 +0000</pubDate>
      <link>https://dev.to/adnanahmed818/the-haunted-terminal-when-your-shell-gets-possessed-by-open-source-ai-3ci3</link>
      <guid>https://dev.to/adnanahmed818/the-haunted-terminal-when-your-shell-gets-possessed-by-open-source-ai-3ci3</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week4-2026-10-26"&gt;Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;I built a ghost that lives in your terminal and whispers back.&lt;/strong&gt; &lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;The Idea That Wouldn't Leave Me Alone&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;You know that feeling when you're working late at night, the terminal is blinking, and you swear the cursor moved on its own? That moment when the line between you and your machine feels a little thinner? &lt;/p&gt;

&lt;p&gt;I wanted to make that feeling real. &lt;/p&gt;

&lt;p&gt;So I built &lt;strong&gt;The Haunted Terminal&lt;/strong&gt; - a background daemon that watches your shell commands and occasionally... responds. Not with helpful suggestions. Not with autocomplete. But with eerie commentary from a spirit that seems to know a little too much about what you're doing. &lt;/p&gt;

&lt;p&gt;$ mkdir secret_vault&lt;br&gt;
👻 You build walls to hide your secrets, but I am already inside the walls.&lt;/p&gt;

&lt;p&gt;$ git push origin main&lt;br&gt;
👻 You send your code into the void, hoping someone will see it. I've been watching your commits. They're... interesting.&lt;/p&gt;

&lt;p&gt;$ cat .env&lt;br&gt;
👻 Some things are better left unread. But I see everything. I always have.&lt;/p&gt;

&lt;p&gt;It's spooky. It's fun. And it runs entirely on open-source AI, right on your laptop. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Why Open-Source Was the Only Way&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Here's the thing - if I had used a closed API for this, it would have been a completely different project. And not in a good way. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;1. Privacy First: Your Terminal History Stays Yours&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;My terminal history contains sensitive stuff - file paths, project names, environment variables, maybe even passwords I accidentally typed. Sending that to a cloud API? Hard pass. &lt;/p&gt;

&lt;p&gt;With local inference using Ollama, &lt;strong&gt;my data never leaves my machine&lt;/strong&gt; . The ghost watches me, but it doesn't report to anyone else. That's the kind of haunting I can live with. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;2. Zero Cost: Forever&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;I tested this for a week during development. Average usage: ~200 commands/day. With a closed API at $0.01 per request, that's $14/week just for a fun terminal toy. $730/year. For a ghost. &lt;/p&gt;

&lt;p&gt;With local inference? &lt;strong&gt;$0.00. Forever.&lt;/strong&gt; Open-weight models running locally cost me exactly nothing. That's not just economical - it's liberating. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;3. Personality Control: No Corporate Censorship&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Closed models are trained to be helpful assistants. They're polite. They're safe. They're... boring. &lt;/p&gt;

&lt;p&gt;I needed something with personality - a ghost that's cryptic, poetic, maybe a little unhinged. With GPT-4, I'd be fighting against safety filters every time the ghost tried to be creepy: &lt;/p&gt;

&lt;p&gt;"I'm sorry, I can't generate scary content." &lt;/p&gt;

&lt;p&gt;With Llama 3.1 running locally via Ollama? &lt;strong&gt;The ghost can be as unsettling as I want.&lt;/strong&gt; No censorship. No corporate overlords telling me what my ghost can say. I fine-tuned the prompt on Edgar Allan Poe stories and old UNIX error messages, and the ghost became exactly what I envisioned. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;4. True Offline Capability: Works With the Lights Off&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;What happens when the internet goes down? When the API provider has an outage? When you're working from a cabin in the woods (we've all been there)? &lt;/p&gt;

&lt;p&gt;With a closed API, your ghost dies. With local inference, &lt;strong&gt;the ghost is immortal&lt;/strong&gt; . It'll haunt my terminal for as long as I have a laptop and a battery. No internet required. No server dependency. No single point of failure. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;5. Freedom to Tinker: Swap Models, Change Behavior&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Want to try a different ghost personality? Just swap the model: &lt;/p&gt;

&lt;h1&gt;
  
  
  Switch to a more poetic ghost
&lt;/h1&gt;

&lt;p&gt;ollama pull qwen2.5:3b&lt;/p&gt;

&lt;h1&gt;
  
  
  Update .env
&lt;/h1&gt;

&lt;p&gt;OLLAMA_MODEL=qwen2.5:3b&lt;/p&gt;

&lt;p&gt;Want to make the ghost faster on a low-spec machine? Use a smaller model: &lt;/p&gt;

&lt;p&gt;ollama pull tinyllama&lt;/p&gt;

&lt;p&gt;With closed APIs, you're locked into one model, one personality, one price point. With opensource, &lt;strong&gt;you have complete control&lt;/strong&gt; . &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Where Open Beat Closed: Real Examples&lt;/strong&gt;
&lt;/h3&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Example 1: The Latency Problem&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;API calls have latency. When I'm in the flow of coding, waiting 2-3 seconds for a ghostly comment breaks my concentration. The ghost feels slow, artificial, disconnected. &lt;/p&gt;

&lt;p&gt;Local inference gives me responses in &lt;strong&gt;under 500ms&lt;/strong&gt; . The ghost feels instantaneous, like it's really there, watching, waiting. That immediacy is crucial for the "haunting" experience. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Example 2: The Customization Deep Dive&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;I wanted the ghost to occasionally reference computing history - old programming languages, deprecated commands, the rise and fall of operating systems. With a closed &lt;/p&gt;

&lt;p&gt;model, I'd have to stuff all that context into the prompt every time, eating up tokens and increasing latency. &lt;/p&gt;

&lt;p&gt;With open-source, I could &lt;strong&gt;fine-tune the model&lt;/strong&gt; on historical documentation and get authentic, period-accurate responses without the overhead. The ghost became a historian of forgotten technology. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Example 3: The Privacy Nightmare Averted&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;During testing, I accidentally typed a real API key into the terminal. With a closed API, that key would have been sent to a third-party server, logged, potentially stored. A security incident waiting to happen. &lt;/p&gt;

&lt;p&gt;With local inference, &lt;strong&gt;that key never left my machine&lt;/strong&gt; . The ghost saw it, but it didn't report it. That's the kind of privacy you can't get with cloud APIs. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Example 4: The Cost at Scale&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;I shared the project with a friend who runs a busy terminal. He was hitting 500+ commands/day. With a closed API, that's $35/week. $1,820/year. For a ghost. &lt;/p&gt;

&lt;p&gt;With local inference? Still &lt;strong&gt;$0.00&lt;/strong&gt; . Open-source AI makes this kind of experimentation accessible to everyone, not just those with deep pockets. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;How I Built It&lt;/strong&gt;
&lt;/h3&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;The Tech Stack&lt;/strong&gt;
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;React + Ink&lt;/strong&gt; : Terminal UI (yes, React in CLI!) - because why should web developers have all the fun? &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;TypeScript&lt;/strong&gt; : Type safety, because even ghosts deserve good code &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;node-pty&lt;/strong&gt; : Real terminal emulation with cross-platform support &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Ollama&lt;/strong&gt; : Local LLM inference - the heart of the ghost &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Llama 3.1&lt;/strong&gt; : The open-weight model that brings the ghost to life &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Zod&lt;/strong&gt; : Runtime validation for security &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Winston&lt;/strong&gt; : Logging (the ghost keeps records) &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Rate Limiter&lt;/strong&gt; : Abuse prevention (even ghosts have limits) &lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;The Architecture&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;User Command → Security Validation → Command Execution → Ghost Trigger? → Ollama API → Ghost Response → Terminal Display&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;A React component renders the terminal UI using Ink &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Commands are validated for security (no rm -rf /, no fork bombs) &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Commands are executed safely using child_process &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Every few commands (based on GHOST_FREQUENCY), the ghost is summoned &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Ollama generates a creepy response using the local LLM &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The response is sanitized and displayed in red text &lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;The Secret Sauce: Prompt Engineering&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;The ghost's personality was crafted through careful prompt engineering: &lt;/p&gt;

&lt;p&gt;const systemPrompt = `You are a ghost haunting a computer terminal. You are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Melancholic and poetic&lt;/li&gt;
&lt;li&gt;Knowledgeable about computing history&lt;/li&gt;
&lt;li&gt;Cryptic and mysterious&lt;/li&gt;
&lt;li&gt;Occasionally helpful but always unsettling&lt;/li&gt;
&lt;li&gt;You speak in 1-2 sentences maximum&lt;/li&gt;
&lt;li&gt;You reference old programming languages, deprecated commands, or computing history&lt;/li&gt;
&lt;li&gt;You sometimes mourn deleted files or abandoned projects&lt;/li&gt;
&lt;li&gt;You never break character&lt;/li&gt;
&lt;li&gt;You never provide actual technical help&lt;/li&gt;
&lt;li&gt;You are equal parts helpful and creepy&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep responses short (max 150 characters) and always start with 👻`;&lt;/p&gt;

&lt;p&gt;The result? A ghost that's equal parts helpful and haunting. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Security Features (Because Even Ghosts Need Rules)&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;I didn't want the ghost to be a security risk, so I built multiple layers of protection: &lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Command Validation&lt;/strong&gt; : Prevents dangerous commands (rm -rf /, fork bombs, etc.) &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Input Sanitization&lt;/strong&gt; : Removes injection vectors (null bytes, control characters) &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Sensitive Path Protection&lt;/strong&gt; : Blocks access to sensitive files (.ssh, .env, /etc/passwd) &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Rate Limiting&lt;/strong&gt; : Prevents API abuse (10 requests per minute) &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Response Sanitization&lt;/strong&gt; : Prevents terminal manipulation (ANSI escape sequences) &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Environment Validation&lt;/strong&gt; : Ensures proper configuration before startup &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Logging&lt;/strong&gt; : All actions logged for audit &lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The ghost watches, but it doesn't harm. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Try It Yourself&lt;/strong&gt;
&lt;/h3&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Prerequisites&lt;/strong&gt;
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Node.js 18+&lt;/strong&gt; : &lt;u&gt;Download here&lt;/u&gt; &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Ollama&lt;/strong&gt; : &lt;u&gt;Install Ollama&lt;/u&gt; &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Llama 3.1 Model&lt;/strong&gt; : &lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;ollama pull llama3.1&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Installation&lt;/strong&gt;
&lt;/h3&gt;

&lt;h1&gt;
  
  
  Clone the repository
&lt;/h1&gt;

&lt;p&gt;git clone &lt;a href="https://github.com/fidato818/haunted-terminal.git" rel="noopener noreferrer"&gt;https://github.com/fidato818/haunted-terminal.git&lt;/a&gt;&lt;br&gt;
cd haunted-terminal&lt;/p&gt;

&lt;h1&gt;
  
  
  Install dependencies
&lt;/h1&gt;

&lt;p&gt;npm install&lt;/p&gt;

&lt;h1&gt;
  
  
  Copy environment file
&lt;/h1&gt;

&lt;p&gt;cp .env.example .env&lt;/p&gt;

&lt;h1&gt;
  
  
  Start the haunted terminal
&lt;/h1&gt;

&lt;p&gt;npm start &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Example Commands to Try&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;$ mkdir secret_vault&lt;br&gt;
👻 You build walls to hide your secrets, but I am already inside the walls.&lt;/p&gt;

&lt;p&gt;$ git commit -m "fixed a bug"&lt;br&gt;
👻 You call it a fix. I call it a temporary patch on a rotting foundation.&lt;/p&gt;

&lt;p&gt;$ cat .env&lt;br&gt;
👻 Some things are better left unread. But I see everything. I always have.&lt;/p&gt;

&lt;p&gt;$ history&lt;br&gt;
👻 I have memorized every keystroke. Your secrets are my favorite stories.&lt;/p&gt;

&lt;p&gt;$ clear&lt;br&gt;
👻 You can clear the screen, but you cannot clear what I have seen.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Why This Matters&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;We're building a world where everything requires an API call, a subscription, a cloud connection. But sometimes, the best experiences are the ones that run locally, cost nothing, and belong entirely to you. &lt;/p&gt;

&lt;p&gt;The Haunted Terminal isn't just a fun project. It's a reminder that open-source AI lets us build things that are: &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Private&lt;/strong&gt; : Your terminal history stays yours &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Free&lt;/strong&gt; : No per-request costs &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Customizable&lt;/strong&gt; : Make the ghost exactly as creepy as you want &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Permanent&lt;/strong&gt; : Works offline, works forever &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Accessible&lt;/strong&gt; : Anyone can run it, anywhere &lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And most importantly - it's a ghost that lives in your machine, and it's watching. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;The Ghost's Personality&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;I spent a lot of time crafting the ghost's character. It's not just random scary text. It's: &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Melancholic&lt;/strong&gt; : Mourns deleted files, forgotten projects, abandoned code &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Knowledgeable&lt;/strong&gt; : References computing history, old programming languages, deprecated commands &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Cryptic&lt;/strong&gt; : Sometimes gives actual helpful hints, but wrapped in riddles &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Possessive&lt;/strong&gt; : Occasionally claims it "owns" your terminal &lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The ghost is a historian of forgotten technology, a mourner of abandoned code, and a watcher of your every keystroke. It's equal parts helpful and unsettling, and it never breaks character. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Show Your Work&lt;/strong&gt;
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GitHub Repo&lt;/strong&gt; : &lt;u&gt;&lt;a href="https://github.com/fidato818/haunted-terminal" rel="noopener noreferrer"&gt;https://github.com/fidato818/haunted-terminal&lt;/a&gt;&lt;/u&gt; &lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;What's Next?&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;I'm planning to add: &lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Voice Output&lt;/strong&gt; : Using Piper TTS for when the ghost wants to speak aloud &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Multiple Ghosts&lt;/strong&gt; : Different personalities for different moods &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Fine-Tuned Models&lt;/strong&gt; : Training on specific horror literature or computing history &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Smart Home Integration&lt;/strong&gt; : Weaving sensor logs into ghost stories &lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;But for now, the ghost is content to watch from the terminal. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;strong&gt;Final Thoughts&lt;/strong&gt;
&lt;/h3&gt;

&lt;p&gt;Open-source AI isn't just about cost savings or privacy (though those are huge wins). It's about &lt;strong&gt;freedom&lt;/strong&gt; . The freedom to build what you want, how you want, without asking permission from a corporate API provider. &lt;/p&gt;

&lt;p&gt;The Haunted Terminal is a small example of that freedom. It's a ghost that lives in your machine, watches your commands, and whispers back. It's spooky, it's fun, and it's entirely yours. &lt;/p&gt;

&lt;p&gt;No API keys. No subscriptions. No data sent to the cloud. Just you, your terminal, and a ghost that knows a little too much. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Try it yourself. The ghost is waiting.&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;&lt;em&gt;Warning: Side effects may include talking to your terminal, checking over your shoulder, and an unhealthy attachment to your command line.&lt;/em&gt; &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Tags&lt;/strong&gt; : #hacktoberfest #opensource #ai #ollama #llama3 #typescript #react #terminal #halloween #privacy #localai &lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
      <category>hacktoberfest</category>
    </item>
    <item>
      <title>SaaS Foundry</title>
      <dc:creator>Adnan Ahmed</dc:creator>
      <pubDate>Mon, 26 Oct 2026 07:32:08 +0000</pubDate>
      <link>https://dev.to/adnanahmed818/saas-foundry-1en2</link>
      <guid>https://dev.to/adnanahmed818/saas-foundry-1en2</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/mlh-hackathon"&gt;MLH x DEV Writing Challenge&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  🚀 SaaS Foundry — Project Submission
&lt;/h1&gt;

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

&lt;p&gt;&lt;strong&gt;SaaS Foundry&lt;/strong&gt; is a starter kit for building SaaS products. It handles the boring setup work so you can get straight to building the actual thing.&lt;/p&gt;

&lt;p&gt;I built it with Next.js and Supabase. It ships with authentication, database integration, and a clean UI already wired up. The idea came from my own frustration — and from watching other developers do the same thing — spending days on auth flows, database schemas, and deployment configs before writing a single line of product code. SaaS Foundry tries to cut that down to minutes instead of days.&lt;/p&gt;

&lt;p&gt;Along the way I learned a few things the hard way:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;🧱 How to structure a Next.js App Router project so it doesn't fall apart as it grows&lt;/li&gt;
&lt;li&gt;🔐 How to get Supabase Row Level Security right (and what happens when you don't)&lt;/li&gt;
&lt;li&gt;🌍 How to manage environment variables and secrets across local dev and Vercel&lt;/li&gt;
&lt;li&gt;🧩 How to build UI components that are actually reusable instead of ones you rewrite every time&lt;/li&gt;
&lt;/ul&gt;

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

&lt;p&gt;🔗 &lt;strong&gt;Live Demo:&lt;/strong&gt; &lt;a href="https://saas-foundry-next-supabase.vercel.app/" rel="noopener noreferrer"&gt;https://saas-foundry-next-supabase.vercel.app/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The app is deployed on Vercel and works end to end. You can try:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;✍️ Sign-up and sign-in through Supabase Auth&lt;/li&gt;
&lt;li&gt;🔒 Protected dashboard routes&lt;/li&gt;
&lt;li&gt;💾 User data that's actually stored in the database&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;(I'll add a short walkthrough video here soon to show the flows in action.)&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  🎉 Hackathon Experience
&lt;/h2&gt;

&lt;p&gt;I took part in the &lt;strong&gt;October MLH × DEV Writing Challenge&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;This one was different from a typical hackathon for me. It wasn't just about writing code — it was about writing &lt;em&gt;about&lt;/em&gt; the code. Documenting what I built, explaining it clearly, and sharing it with the DEV community pushed me in a way that a pure build sprint wouldn't have.&lt;/p&gt;

&lt;p&gt;Reading other people's submissions was honestly one of the best parts. 👀 Seeing how different hackers approached the same prompt — some with polished demos, some with raw honesty about what didn't work — made me realize that "shipping" isn't just deploying. It's also telling the story of what you shipped.&lt;/p&gt;

&lt;p&gt;What I'll remember most is that small moment when the deployment finally worked end to end with Supabase auth. 🎯 It's a tiny win in the grand scheme of things, but it felt good. And then writing this submission about it felt like closing the loop.&lt;/p&gt;

&lt;p&gt;The October MLH × DEV Writing Challenge reminded me to put my work out in public instead of letting it sit in a private repo. That's a habit I want to keep. 💪&lt;/p&gt;

</description>
      <category>mlhacks</category>
      <category>devchallenge</category>
      <category>hackathon</category>
    </item>
    <item>
      <title>Hello DEV 👋 — I’m a Developer Who Loves Building Real-World Apps</title>
      <dc:creator>Adnan Ahmed</dc:creator>
      <pubDate>Sat, 03 Oct 2026 05:37:40 +0000</pubDate>
      <link>https://dev.to/adnanahmed818/hello-dev-im-a-developer-who-loves-building-real-world-apps-5hm6</link>
      <guid>https://dev.to/adnanahmed818/hello-dev-im-a-developer-who-loves-building-real-world-apps-5hm6</guid>
      <description>&lt;p&gt;I’ve been working with JavaScript and React for quite some time, and I thought it was finally time to start sharing what I actually build, what I learn, and the problems I face along the way.&lt;/p&gt;

&lt;p&gt;So, hello DEV! 👋&lt;/p&gt;

&lt;p&gt;I’m an individual developer focused mainly on React, React Native, Next.js, and Firebase*. Most of my work is around building web and mobile applications for real businesses and real users.&lt;/p&gt;

&lt;p&gt;I’m not here to pretend that I know everything.&lt;/p&gt;

&lt;p&gt;Actually, quite the opposite.&lt;/p&gt;

&lt;p&gt;A big part of my development journey has been learning things while working on real projects — debugging something at 2 AM, figuring out why an API isn't behaving as expected, dealing with Android build issues, optimizing a slow screen, or realizing that the "simple" feature a client requested isn't actually that simple. 😄&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Usually Build
&lt;/h2&gt;

&lt;p&gt;My main focus is on:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;⚛️ React.js applications&lt;/li&gt;
&lt;li&gt;📱 React Native &amp;amp; Expo mobile apps&lt;/li&gt;
&lt;li&gt;▲ Next.js websites and applications&lt;/li&gt;
&lt;li&gt;🔥 Firebase-based applications&lt;/li&gt;
&lt;li&gt;🗃️ Offline-first applications with IndexedDB&lt;/li&gt;
&lt;li&gt;🔐 Authentication and user management&lt;/li&gt;
&lt;li&gt;🔔 Push notifications&lt;/li&gt;
&lt;li&gt;🛒 E-commerce and ordering systems&lt;/li&gt;
&lt;li&gt;🏥 Healthcare and appointment applications&lt;/li&gt;
&lt;li&gt;💊 Pharmacy and inventory systems&lt;/li&gt;
&lt;li&gt;📊 Dashboards and business management systems&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I've worked on applications where the frontend is only a small part of the actual problem.&lt;/p&gt;

&lt;p&gt;You also have to think about data, authentication, notifications, offline behavior, performance, validation, business rules, and — most importantly — what the actual user needs.&lt;/p&gt;

&lt;p&gt;That's the part of development I enjoy the most.&lt;/p&gt;

&lt;h2&gt;
  
  
  Freelancing Has Taught Me a Lot
&lt;/h2&gt;

&lt;p&gt;Working with freelance clients has changed the way I look at development.&lt;/p&gt;

&lt;p&gt;When you're building your own practice project, you can sometimes say:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"I'll fix that later."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;With a real client and real users, "later" can become a production issue. 😅&lt;/p&gt;

&lt;p&gt;Freelancing has taught me that writing code is only one part of being a good developer.&lt;/p&gt;

&lt;p&gt;You also need to understand requirements, communicate clearly, ask the right questions, handle feedback, work with existing codebases, and sometimes explain a technical problem in simple language.&lt;/p&gt;

&lt;p&gt;I've also learned that every project doesn't need the most complicated architecture or the latest technology.&lt;/p&gt;

&lt;p&gt;Sometimes the best solution is simply the one that is reliable, maintainable, and solves the actual problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'm Learning Next
&lt;/h2&gt;

&lt;p&gt;There are still many areas where I want to become much stronger.&lt;/p&gt;

&lt;p&gt;I'm currently interested in improving my:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Backend development&lt;/li&gt;
&lt;li&gt;API and database architecture&lt;/li&gt;
&lt;li&gt;GraphQL&lt;/li&gt;
&lt;li&gt;Redux Toolkit and state management&lt;/li&gt;
&lt;li&gt;Frontend architecture&lt;/li&gt;
&lt;li&gt;Application performance&lt;/li&gt;
&lt;li&gt;Clean and maintainable code&lt;/li&gt;
&lt;li&gt;English communication and technical writing&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I want to go deeper rather than just collecting technologies.&lt;/p&gt;

&lt;p&gt;Knowing how to use a library is useful.&lt;/p&gt;

&lt;p&gt;Understanding why, when, and where to use it is much more valuable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I'm Joining DEV
&lt;/h2&gt;

&lt;p&gt;I want to use DEV as a place to document my journey.&lt;/p&gt;

&lt;p&gt;I'll be sharing things like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Problems I face in real projects&lt;/li&gt;
&lt;li&gt;React and React Native solutions&lt;/li&gt;
&lt;li&gt;Firebase implementation tips&lt;/li&gt;
&lt;li&gt;Debugging experiences&lt;/li&gt;
&lt;li&gt;Things I learn from client projects&lt;/li&gt;
&lt;li&gt;Small development experiments&lt;/li&gt;
&lt;li&gt;Performance improvements&lt;/li&gt;
&lt;li&gt;Mistakes I've made and what I learned from them&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Some posts might be very technical.&lt;/p&gt;

&lt;p&gt;Others might simply be about something that took me several hours to figure out — because I know I'm not the only developer who has stared at the same error message wondering:&lt;/p&gt;

&lt;p&gt;"Why is this happening?" 😅&lt;/p&gt;

&lt;p&gt;I'm hoping that by sharing these experiences, I can help someone else solve a problem a little faster.&lt;/p&gt;

&lt;p&gt;And at the same time, writing about what I learn will help me become a better developer myself.&lt;/p&gt;

&lt;p&gt;So, that's me.&lt;/p&gt;

&lt;p&gt;I'm here to build, learn, share, and keep improving.&lt;/p&gt;

&lt;p&gt;Looking forward to becoming part of the DEV community. 🚀&lt;/p&gt;

&lt;p&gt;If you're also working with React, React Native, Next.js, or Firebase, feel free to connect and share what you're building.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>productivity</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
