@GetPrbl · X

@Aryandwi007 · X

Hey check this out

@satulipa_ · X

My workflow: 1. Open Speckit → answer 5 questions 2. Get blueprint (PRD, DB, API, roadmap) 3. Take it to Cursor/Claude Code 4. Vibe code with actual direction Built with Next.js, Vercel, try it on

@preproomai · X

🟢Get ready for #vibecoding and AI #codereview. It is cutting-age & you can't miss: Time to ditch old-school @LeetCode ! #SoftwareEngineering #TechInterviews #CodingSkills #TechCareers #PrepRoom #TechCareers #SystemDesign #ITJobs #CareerGrowth

@aarsh_30 · X

@mkappworks · X

I am building lets connect

@atenyun · X

Hi everyone! If you're getting into vibe coding and have questions about LSPs or need a hand with reviewing your smart contract, feel free to post on Hup. We're here to help you out! Creator: 0x20e229667Cec8A0e9D3C6Fb89693B2a44ec2C50e via @hupsocial

rsproule · HN

Share and explore custom Claude Code status lines

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.

videlov · HN

I was interested in answering this question so I built a benchmark comparing git, jj and gitbutler in agentic context https://vcbench.dev/ Disclaimer - I am a co-founder of GitButler

@notunknownkyun · X

- leetcode style interview prep for agentic AI interviews and unskilling folks.

@Michaela200_5 · X