Hey, I’m KLKA 👋

Sometimes projects don’t have to solve a serious problem — they just need to be fun, a little bit cursed, and technically interesting. I recently built a small web app CommitFill where a user can select arbitrary dates, hit submit, and the app will automatically create Git commits on those exact dates. Those commits then appear on the GitHub contribution graph like they were made back in time. Yes — it’s basically time travel for commits 🕰️ ...

During my first hackathon, I built a project hosted on Render. I was excited to get it working quickly, so I used Supabase for everything — database, authentication, even storing media. It worked… but it was slow and sometimes unreliable. After the hackathon, I optimized it so the project could stay online, recover from Render’s file deletions, and run much faster. 🚩 The Original Setup Supabase Database stored all app data plus media files (images, uploads). Render hosted the app, but free-tier instances delete local files regularly. Because every read/write hit Supabase, queries felt sluggish. Storing media in the DB made things even heavier. 🔧 The Optimizations 1. Dual Database Setup I introduced SQLite as the primary DB (fast local reads/writes). Supabase DB remained the source of truth + persistent backup. I wrote a script that: Detects when Render deletes the local SQLite file. Pulls fresh data from Supabase. Recreates a new SQLite database from it. 👉 Result: SQLite gives speed, Supabase ensures persistence, and the script automatically heals the system when Render wipes local files. ...