@sykatt01 · X

Here it is: Definitely appreciating feedbacks

@KSFirasa · X

Hello! I built a tool that profiles code (python only atm) across 14 dimensions detecting violations and capabilities outputting a full report. A bit more nuanced than "AI-powered insights". Free while in beta. Thank you!

@SinghApurv1711 · X

Hey! Check it out here:

@TheSarimQureshi · X

othmanosx · HN

I still don't like the fact that AI is adding more stuff for us to read, it's accelerating the code production but slowing down the code review. I built my own code reviewer as well ( https://pyor.review/ ), surfacing the important stuff first is the right track, but adding more stuff to read is daunting, but asking AI to just point you to what you need to focus on and skim the noise is what I'm leaning more towards.

@sadmandu55 · X

@itz_sayan_03 · X

Ever wondered how cinematic scroll-driven websites are built? 👀 Meet SectionFlow—an open-source React library with 60+ ready-to-use section transitions, a one-command CLI, reusable sections, and optimized performance. 🚀

@md_shadann · X

@GetPrbl · X

@SpecParse · X

Convert Complex PDF Tables into Styled Excel Workbooks

u/Still_Amphibian545 · Reddit

almost launched a side project with my api keys sitting in the repo (a week free gpt 5.6 on us) was about a day from launching a small project when i noticed my openai key was just sitting in a committed file. it had been there for weeks. no idea how i missed it. made me wonder what else was wrong that i couldn't see. turns out for vibecoded stuff it's usually the same handful of things. secrets in the repo, endpoints with no auth, a database with no access rules, no limit on the ex

forgeapp