<?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: leppercaun22</title>
    <description>The latest articles on DEV Community by leppercaun22 (@leppercaun22_58f090dde953).</description>
    <link>https://dev.to/leppercaun22_58f090dde953</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%2F4256257%2Fe9bead36-ebe6-4be9-a98e-172ffef82ce8.png</url>
      <title>DEV Community: leppercaun22</title>
      <link>https://dev.to/leppercaun22_58f090dde953</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/leppercaun22_58f090dde953"/>
    <language>en</language>
    <item>
      <title>The Week My App Almost Ran Out of Database</title>
      <dc:creator>leppercaun22</dc:creator>
      <pubDate>Fri, 20 Nov 2026 23:55:34 +0000</pubDate>
      <link>https://dev.to/leppercaun22_58f090dde953/the-week-my-app-almost-ran-out-of-database-2jj0</link>
      <guid>https://dev.to/leppercaun22_58f090dde953/the-week-my-app-almost-ran-out-of-database-2jj0</guid>
      <description>&lt;p&gt;Hey dev.to — Lepp again. Entry two in building &lt;strong&gt;Neuro-Kindred&lt;/strong&gt; (a free, calm social app for neurodivergent adults, 18+) in the open. Last time: pebbles instead of likes. This time: a mystery, three wrong suspects, and the week I nearly lost the whole app to a free-tier limit.&lt;/p&gt;

&lt;h2&gt;
  
  
  The setup
&lt;/h2&gt;

&lt;p&gt;Neuro-Kindred runs on a $3/month server and a free Postgres database (Neon, 100 free compute-hours a month). On Nov 15 I got the email nobody wants: &lt;strong&gt;80 of the 100 hours already used&lt;/strong&gt;, halfway through the month. At 100, the database sleeps until December 1st — app down, no charge, data safe, but down.&lt;/p&gt;

&lt;p&gt;Something was waking the database constantly. It wasn't my members: in the worst 48-hour stretch, 38 members sent 63 messages total. So I went hunting.&lt;/p&gt;

&lt;h2&gt;
  
  
  Suspect #1: the scanners
&lt;/h2&gt;

&lt;p&gt;The server logs showed a burst of 188 requests in one minute from a cloud IP, probing for &lt;code&gt;.env&lt;/code&gt; files and admin paths. All 404s, nothing exposed — but bots were my first theory. Verdict: real, but too small. The burn continued on quiet nights with no scanner traffic at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  Suspect #2: the old deployment
&lt;/h2&gt;

&lt;p&gt;The app used to live on an app-builder platform before I moved it to my own server. Maybe the old copy was still running somewhere, pinging away? I unpublished it (Nov 17) and measured for 24 hours. The burn barely moved. Not the culprit — and now I couldn't easily un-unpublish my main suspect.&lt;/p&gt;

&lt;h2&gt;
  
  
  Suspect #3: my own forgotten robots
&lt;/h2&gt;

&lt;p&gt;This one stung. Back in September, the builder era set up &lt;strong&gt;two&lt;/strong&gt; keep-alive jobs (duplicates, of course) pinging the app's health endpoint every 5 minutes — and every ping runs database queries, and every query resets the database's 5-minute idle timer. The database was being politely woken up 24/7 by robots I owned. I disabled both (Nov 15) and the sleep test passed... but the daily burn only dropped a little. A contributor. Not the culprit.&lt;/p&gt;

&lt;h2&gt;
  
  
  The actual culprit: the app itself
&lt;/h2&gt;

&lt;p&gt;The final measurement read the request logs by endpoint. In 48 hours: &lt;strong&gt;the calls screen had been checked 3,497 times&lt;/strong&gt; — about once every 3 seconds — from one or two phones with the page left open. Message threads every 4–5 seconds. Game rooms every 2 seconds. My own app's screens were the waker. One member leaving the app open on their phone was costing more database than every real conversation combined.&lt;/p&gt;

&lt;p&gt;The fix shipped Nov 20: the calls overview now checks every 20 seconds, message threads every 10 (pausing entirely when the tab is hidden was already in there — the problem was never hidden tabs, it was &lt;em&gt;visible&lt;/em&gt; ones being impatient). Full test suite green (552 tests), and I'm re-measuring for 24 hours before I claim it worked. If the number doesn't drop, I'll say so in entry three.&lt;/p&gt;

&lt;h2&gt;
  
  
  The honest numbers
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Database: 86.3 of 100 free hours used (Nov 18 reading)&lt;/li&gt;
&lt;li&gt;Members: 38 · Revenue: $0 · Server: $3/month&lt;/li&gt;
&lt;li&gt;Cost of the investigation: a few evenings and one unpublished old site&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Lesson:&lt;/strong&gt; on a free tier, &lt;em&gt;your own polling is your biggest user.&lt;/em&gt; Measure by endpoint before you blame the internet.&lt;/p&gt;

&lt;h2&gt;
  
  
  One question before you go
&lt;/h2&gt;

&lt;p&gt;Neuro-Kindred runs a community night every &lt;strong&gt;Friday, 7pm CT&lt;/strong&gt; (trivia, a game, then a watch-together on Discord) — it's the hour the app feels most like itself. &lt;strong&gt;Comment with the interest you could talk about for a full hour, and I'll send you an invite to this Friday's.&lt;/strong&gt; That's the whole exchange — your weird topic for a seat at the table. It's also literally what the app is for.&lt;/p&gt;

&lt;p&gt;— Lepp&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Next entry: "Pebbles grow old now" — why an unanswered pebble sitting in limbo forever is unkind, and the 30-day close we just shipped.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>buildinpublic</category>
      <category>showdev</category>
      <category>webdev</category>
      <category>postgres</category>
    </item>
    <item>
      <title>I Built a Calm Social App Solo With an AI App Builder — Pebbles Instead of Likes, and Three Strikes You're Out</title>
      <dc:creator>leppercaun22</dc:creator>
      <pubDate>Fri, 20 Nov 2026 19:05:34 +0000</pubDate>
      <link>https://dev.to/leppercaun22_58f090dde953/i-built-a-calm-social-app-solo-with-an-ai-app-builder-pebbles-instead-of-likes-and-three-strikes-26mp</link>
      <guid>https://dev.to/leppercaun22_58f090dde953/i-built-a-calm-social-app-solo-with-an-ai-app-builder-pebbles-instead-of-likes-and-three-strikes-26mp</guid>
      <description>&lt;p&gt;Hey dev.to — I'm Lepp, and I've spent the last few months building &lt;strong&gt;Neuro-Kindred&lt;/strong&gt;, a free web app (installable PWA) for neurodivergent adults (18+) to find friends or dates. I built it solo on an AI app-builder called cto.new, which means my whole workflow looks a little unusual: I write the specs, the builder's AI writes the code, and then I make it try to break its own work in a deep debug audit.&lt;/p&gt;

&lt;p&gt;I'm sharing the interesting product and technical choices, because a few of them were genuinely hard to get right.&lt;/p&gt;

&lt;h2&gt;
  
  
  The app
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://neuro-kindred.com/discover" rel="noopener noreferrer"&gt;https://neuro-kindred.com/discover&lt;/a&gt; — and a no-account-needed demo with sample profiles and playable games: &lt;a href="https://neuro-kindred.com/demo" rel="noopener noreferrer"&gt;https://neuro-kindred.com/demo&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Feature list, briefly: context-rich profiles, an AI bio helper and AI match explanations, messaging, voice/video calls, Connect Four and group trivia games, watch-together rooms, calm accessible design. Public pages in six languages (English, Español, Français, Deutsch, Português, हिन्दी). Sign-up is username/email/password/date-of-birth only — no country field, open worldwide. No paywall, no subscriptions; there's an optional one-time tip jar ($2/$5/$10/$20) that nobody has used yet. Honest status: 13 real members, $0 revenue.&lt;/p&gt;

&lt;h2&gt;
  
  
  The interesting choices
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. "Shiny pebbles" instead of likes.&lt;/strong&gt; No like counters, no match percentages, no read receipts pressure. You give someone a pebble — a small, deliberate signal. The reason it's a technical story: double-sending a pebble was a real race condition (two taps, two pebbles, awkward). The fix went to the database layer — partial unique indexes plus a Postgres trigger guarding the count. Same treatment for game room joins and room caps. It taught me that for a social app, every interaction counter is a race condition waiting to happen, and the only place to fix it for real is the DB.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Read-only demo mode.&lt;/strong&gt; The demo is a fully interactive tour with sample profiles, games, and a watch room — but every locked action opens a "create a free account" dialog instead of writing to the database. The audit verified zero DB writes from the demo. It's a meaningful amount of engineering to let strangers click around a social app without creating accounts, and it was worth it: it's the first thing I'd send anyone.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. A three-strike moderation system, by design not by ML.&lt;/strong&gt; I'm building this right now: strike one is an automatic in-app warning, strike two is a final warning, strike three (from a &lt;em&gt;third different&lt;/em&gt; member) deletes the account. The design constraints were the interesting part — a strike counts only from a distinct reporter, so one person can't mass-report someone out of existence; self-reports don't count; admins get a pardon/reset override; warning copy had to be written in all six languages with the same calm tone. No email system exists, so everything is in-app. Coordinated-report abuse is the residual risk and I'm not pretending it's solved.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Language support that doesn't break the PWA.&lt;/strong&gt; The picker sits on all eight public pages, works logged-out, honors &lt;code&gt;?lang=&lt;/code&gt; parameters, and persists via a cookie. Partial translation is worse than none if it surprises people, so I documented exactly what stays English (the demo is effectively English-only for now) rather than claiming full coverage.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lessons
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The audit habit compounds.&lt;/strong&gt; The deep debug I run on this app (build, 200+ tests, secrets scan, route checks, protected-API checks, DB census) catches the boring defects that would be catastrophic in a social app: orphaned rooms, race conditions, missing report paths. Spec the audit, don't just ship.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AI builders move fast and break social invariants.&lt;/strong&gt; The fastest code to write is the most optimistic code — no double-click handling, no concurrent-join logic. For a social app, "what happens when two people do this at once" is the first question, not the last.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Distribution is the actual hard part.&lt;/strong&gt; The build was the fun half. Thirteen real members came one at a time through directories, permission-first subreddit posts, and international ND communities. No trick, just slow.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you poke at the demo, I'd genuinely love feedback on two things: (1) what's confusing in the first 60 seconds, and (2) any social-invariant edge cases I clearly haven't thought of — you all are good at that one.&lt;/p&gt;

&lt;p&gt;— Lepp&lt;/p&gt;

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