akifq

6 ms·

1. 1.▲
   Show HN: Shadow VCS quarantines AI generated commits before they break your repo(github.com)

   2 points by akifq 1y ago|0 comments
2. 2.▲
   by akifq 1y ago

   Ran Vibe Kanban on a side repo over the weekend it’s slick, but I tripped on one thing: all the agents write into the same checkout, so parallel cards can clobber each other when they touch the same files. I’ve been spinning up a quick `git
3. 3.▲
   by akifq 1y ago

   In software we already let Copilot rough-draft code, run tests, then keep or toss the changes. We can do the same with hardware: – keep the AI traces in a separate layer or revision – run basic checks for clearance and width – eyeball the d
4. 4.▲
   by akifq 1y ago

   The tricky part is psychological: once you charge, you implicitly promise consumer-grade polish. If the address-bar jitters after an update, people will cancel faster than they would stop donating.
5. 5.▲
   by akifq 1y ago

   Human readability isn’t going away. Most teams still debug by eyeball, so the baseline must stay “another human can scan this at 2 a.m."