Yatharth ( AI native dev )

Just published new version of express-route-cache.js.org - Cache Studio ->unified cache dashboard inspired by prisma studio - Improved Docs - Improved stampede protection for distributed system - Hashed cache keys to reduce sizes - Memory Optimization - Fixed Known issues

@droidbuilds Antigravity 2.0 sucks so the ball is in the cursor hands now

developers, which IDE genuinely has the potential to replace VS Code?

@Aditya_181105 Just a wallpaper

Which windows laptop can handle this?

Google had the best IDE but no more as they removed it's core feature of managing agents & totally broke IDE. I think it's time to switch from @antigravity

@geminicli Really hate this update

Transitioning Gemini CLI users to Antigravity CLI We are unifying our efforts around a single harness and platform, Google Antigravity with four distinct surfaces: • Antigravity 2.0 • Antigravity CLI • Antigravity SDK • Antigravity IDE This will allow us to move faster and give you a streamlined experience wherever you do your best work. Rebuilt in Go for speed, Antigravity CLI is available today and brings robust multi-agent orchestration and asynchronous workflows to your terminal. Important things to know: 1. If you are using Gemini CLI through your Google one account (Google AI Pro or AI Ultra) or through Gemini Code Assist for individuals (free offering) we will be helping you migrate your workflows over the next 30 days. 2. No action required for Enterprise users. Enterprise plans and API keys will continue to be supported in Gemini CLI. Read the full details in our blog post → goo.gle/4eWkUgK

smart-hr-omega.vercel.app building something crazy this time

@_brian_johnson Haven't used codex yet will try

@Yatharth_L Same. Cursor is still the fast editing surface, but Codex is better when I want a second agent chewing on a scoped task.

I used Claude code but hate its limit 😭. Now used gemini cli it's 🔥. Used all day fixing major issues but still 50% usage .

Found critical bugs 🐛 .... Fixed most of them . I need to refactor the UI. Honestly product is great but UI is too mordern tech or web3 inspired.

I finally did it .. Poc is ready Now it's time to polish it

Hi you are HR, CEO or business owner hiring but tired of Fake resume, inconsistent candidate profiles & too much application. I am making a product especially for you & it's not another AI interview that costs x $ per interview that's too expensive .

@_brian_johnson Yes I am also keeping both for the same reason

@Yatharth_L Gemini’s free-tier headroom is nice, but the tradeoff is usually workflow fit. I’d still keep Claude for planning/review and use Gemini for broad cleanup passes.

@alexabelonix Totally agree, Last year I built an interview app that cost 5$ per round no student can afford to pay. I had the product but I realised the audience was wrong and dropped the idea . Now working on the same but for HR MVP is ready but fixing 🪲

Failure is not proof you should quit. It is data. It tells you: the offer was unclear the audience was wrong the timing was bad the system was weak the assumption was false Use the lesson. Change the approach. Keep going. Failure only becomes final when you stop learning from it.

This is why I got lectured at home 💀

Building Something Crazy

@FynCas Claude

Claude + MakeUGC + Veo 3 = $65,065 Launch 200+ ads/day straight from your laptop. No creators No product shoots No $10K/month agencies Recreate top-performing competitor ads—the ethical way. Drop in their ad → choose an avatar → generate high-converting variations. Comment “Claude” and I’ll send the full setup + step-by-step playbook. (must be following)

@hiarun02 Ya man & I did actually

> NO Claude > NO Codex > NO Cursor > NO Copilot Just skill. Can you still ship?

I hate Monday

@romaindewolff I have created multiple doc pipelines for healthcare org handling invoices, lab scan, prescription, insurance & even discharge summary. This was also a crazy scale of 1 million users.

@romaindewolff I totally agree that document processing on the server is a nightmare. U can try some edge ai solution that does orc on the client side similar to google. Also maybe you are zipping docs on the server it's huge load instead save onto S3 and serve from there in email.

I almost killed my company on Friday. $90,000. One Azure bill. Gone. Let me tell you what happened because I think founders need to hear this. We built an amazing document intelligence system at Whisperit. It analyzes our customers' files: PDFs, Word docs, scanned documents, using OCR. It works beautifully and user love it. But we had a bug. A small email with a zip file. Inside the zip, a PDF. Some weird edge case that created an infinite loop in our code. The virtual machine would crash, restart, and try to reprocess the same document. Again. And again. And again. We pay more than one cent per page processed. You can imagine what happened next. I saw the graph and my stomach dropped. An exponential spike. The kind of curve you want to see on your revenue chart (!!) not your cloud bill. The forecast for next month said $400,000+. I thought: this must be a mistake. Emergency 🚨. Check everything. It wasn't a mistake. The worst part? We had a warning. Back in November we had a $25K unusual spike. We fixed it. Added upload limits. I thought we were safe. But I never set a spending cap on Azure. Never set up alerts for unusual usage. I knew I should. I just didn't do it. I went through every stage: Denial → "this can't be right" Anger → screaming at myself Shame → feeling small, really small Tears → first time in a long time I cried that evening. Not because of the money, because I imagined having to close Whisperit. My team. Everything we built. Gone because of one missing setting and my stupidity. The week had been incredible. New version shipping. Lots of new users. Sales going well. Migration going well. Growing the team responsibly. And then Friday hit like a truck. Remember my last post about mistakes? Yeah. We're still making them. Bigger ones. $90,000 is the price of a NICE car. Paid for a bug and a missing checkbox. Here's what I'm doing RIGHT NOW so this never happens again: 1. Hard spending limits on every cloud service — no exceptions 2. Alerts at 50%, 80%, 100% of expected spend 3. Circuit breakers in our processing pipeline — if a document fails 3 times, it stops 4. Weekly cloud cost review — not monthly, weekly 5. Every API endpoint gets a budget ceiling If you're a founder reading this: Go set your spending limits. Today. Right now. Before your next meeting. Before your next coffee. It takes 10 minutes and it could save your company. We move fast. That's our superpower. But speed without guardrails is a bomb with a timer. I know what doesn't kill you makes you stronger. I really hope this one doesn't kill me. Still standing. Barely. Building. 🚀