Coming soon: Vibe Coding, a French book about building with AI when you don't know how to code, and staying in charge once it works. https://t.co/xYFuKPj57C
@Damian_Py_Off Fair point on owning the hardware. Here though the refusal isn't a guardrail of the hosted tool. It's the job I give the reviewer in my loop: check the numbers against the journal and refuse any total that isn't there. That would hold on local hardware too.
@RRomcym Thanks! A timestamp tells you how old a number is—not whether you should still trust it. That’s the distinction I want the dashboard to make clear. Happy to compare notes here!
Episode 5: New HTML, old JavaScript.
A successful deploy still left an old table and broken proof links.
We versioned the modules and restored 211 references. The new table now appears in the browser. Link and animation checks still pending.
@HosseinGorji021 Thanks! The key is a narrow prompt: “Review this exact commit. Show expected vs actual behavior and a reproducible failure—not just ‘looks good.’” ACCEPT covers only that reviewed version, not the next edit. Happy to compare notes here!
@abhinayguptha Yes, that's the Episode 4 rule. Designed / reviewed / not live yet until ACCEPT. Freeze the live listing to the signed after-state and keep Review Notes on that same screen, so the first Search users see what reviewers saw, not a half-cutover.
@maomao000211 Exactly. Colour alone still looked fine after 19h frozen; the stamp is what kills the false "all good" read. Tiny label, fewer wake-ups for nothing.
@k4neHotS@gregory_raymond Non mais le tout début du post charge à mort les exchange crypto qui pour une fois n'y sont pour rien. Je n'aime pas l'injustice, c'est tout.