I checked my database logs and found a Senior Engineer stress-testing my AI 🕵️‍♂️

Hey everyone, Harun here again. I’m the 12-year-old solo dev from Anthiyur, India, building an AI coding mentor (KODA) entirely on my POCO C55 Android phone.

Yesterday, I posted about getting my first 5 stranger users. But today, I did something every founder needs to do: I went on a Supabase Stakeout.

I opened my chats table to see what people were actually asking my AI when they thought nobody was watching. And I found a session from a user named Nerando.

I recognized the name. He was a Senior Software Engineer from Atlanta, GA who had given my previous Dev.to post a 🦄 Unicorn reaction. But he didn't just click around my app. He ran a professional, 6-point QA stress test on it.

Here is exactly how a senior engineer interviews a 12-year-old's app:

🧪 The 6-Point Stress Test

1. The UI Test
His first message was exactly one of my "Welcome Chips" (clickable starter prompts). He was checking if my UI shortcuts actually triggered the backend correctly. (Pass ✅)

2. The Core Capability Test
He typed: "Can you code". He didn't want a philosophical answer; he wanted to see if my Groq integration actually generated clean, formatted Python scripts with type hinting. (Pass ✅)

3. The Persona Test
He asked: "What are you". A lot of AI apps break character here and say "I am a large language model trained by..." KODA stayed in character and replied: "I’m KODA – your friendly coding mentor." (Pass ✅)

4. The Edge-Case Test
He clicked my 🆘 Panic Button: "I am confused. Explain simply like I am 5." He was testing if the formatting breaks when the prompt forces a sudden tone shift. KODA gave a clean, emoji-filled, simple explanation. (Pass ✅)

5. The Boundary Test
He asked: "Can you browse". This is a classic dev trap. He wanted to see if the AI would hallucinate and lie about having internet access. KODA correctly admitted its limitations. (Pass ✅)

6. The Deep Domain Test
Finally, he threw a college-level CS concept at it: "I want to know more about abstraction". KODA responded with a masterclass on Procedural vs. Data Abstraction, complete with Python, JS, and Java examples. (Pass ✅)

🧹 The "Janitor Shift" (Cleaning my Database)

While doing the stakeout, I also noticed something else. Out of my 6 total signups, 3 were fake or ghost emails (like [e-mail] which is Turkish for "test").

My older brother (who is an engineering student and my unofficial Board of Directors) asked me: "Why keep them?"

He was right. Fake emails bounce, and high bounce rates destroy your Gmail sender reputation. So I did my first piece of Data Hygiene:

1. I deleted the ghost users from Supabase Auth and the profiles table.
2. I turned Email Confirmations back ON.

Now, bots and fake testers can't pollute my database. A clean database of 3 real humans is worth 100x more than a dirty database of 50 ghosts.

🧠 The Biggest Lesson of Day 2

Stop guessing what features to build. Look at your telemetry.

When I saw another real user (reversality) asking KODA "how to add PWA manifest", I realized I don't need to guess my roadmap. My users are literally typing my to-do list into the chat box.

If you are building a SaaS, go look at your database logs today. What are your users doing when they think you aren't watching?

(P.S. I sent Nerando a "Sniper Email" letting him know I saw his stress test. Fingers crossed he replies!)

Built on a phone in Tamil Nadu. Powered by Supabase, Groq, and Netlify.
Try it if you want: koda-aicodementor.netlify.app