@Jack_Timonen · X

vpetroff · HN

CobaltCode – Dedicated persistent computer for Codex

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.

@0shuvo0 · X

@manoj_surya_ · X

I just launched 🚀 A Proof of Ship, every day — straight from your GitHub. You already do the hard part: you commit. git-to-x turns that into a designed card and posts it to X every morning. Your timeline finally looks like what you actually are — someone who ships. → 8 card designs, rotating (terminal, heatmap, flame, ticker…) so it never gets stale → weekly + monthly milestone cards — your streak becomes a story worth following → tweet from your CLI / Cursor / Claude Code without leaving your editor → free for 10 days, full access See who else is shipping daily under #proofofship — and join them. It touches your repo, so safe-to-try came first: → open source (AGPL) — audit it or self-host → read-only — we never touch your code This is my first build-in-public tool. I built it for myself, and for anyone tired of switching between shipping and posting about shipping. First 100 get founding lifetime — a permanent number on every card. Try it, tell me

u/surmado_rachel · Reddit

We built a cheaper code review tool for small teams We've been working on a code review tool for small teams, solo founders, and vibe coders who want a second set of eyes on every PR without paying Claude-level prices. The idea is simple: Surmado's Scout reviews your PRs against your own standards, not random generic lint rules. You add a STANDARDS.MD file, and on every push Scout gives you: What looks good/What needs work/A short reviewer brief so a human knows where to focus/Feedback

@aka_gaurang · X

There are bounties for creators to grow

@crackedceo · X

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