Andrii Furmanets

hey everyone, figured I'd finally say hello properly after lurking for a while.

I'm Andrii, a freelance full-stack developer based in Lviv, Ukraine. I work mostly with React, Next.js, TypeScript, and Rails - usually helping product teams ship things that have gotten stuck or need a senior hand across both frontend and backend without a ton of overhead.

Last week Garry Tan (CEO of Y Combinator) shared his entire Claude Code setup on GitHub and called it "god mode."

He's sleeping 4 hours a night. Running 10 AI workers across 3 projects simultaneously. And openly saying he rebuilt a startup that once took $10M and 10 people. Alone, with agents.

One recurring issue we ve been seeing with Supabase setups is not the database itself, but how credentials are managed across environments. The common pattern looks something like:

• credentials stored in .env files or secrets managers

• multiple environments (dev, staging, prod)

• manual propagation or duplication across those environments

It works, but over time it seems easy for things to drift:

• a key gets rotated in one environment but not others

• a redeploy misses an env var

• credentials get misconfigured during setup or migration