←back to thread

196 points yuedongze | 2 comments | | HN request time: 0.503s | source
1. pglevy ◴[] No.46199788[source]
I've been thinking about something like this from a UI perspective. I'm a UX designer working on a product with a fairly legacy codebase. We're vibe coding prototypes and moving towards making it easier for devs to bring in new components. We have a hard enough time verifying the UI quality as it is. And having more devs vibing on frontend code is probably going to make it a lot worse. I'm thinking about something like having agents regularly traversing the code to identify non-approved components (and either fixing or flagging them). Maybe with this we won't fall further behind with verification debt than we already are.
replies(2): >>46199816 #>>46201087 #
2. cousinbryce ◴[] No.46201087[source]
That’s just static code analysis with extra steps