10 Hadar
summary
A team builds an internal retrospective app in React TypeScript Tailwind over six months — a few screens and a few thousand lines of code — by vibe coding in React using cursor and cloud code plus Agent MD and Claude MD. Multiple AI sessions create duplicated debounce hooks and four different primary buttons, tests pass but miss integration bugs (a 2s optimistic update assumption breaks production). The team implements sandbox isolation for components with runtime contracts and event-only interfaces to contain drift.
AI-written summary · about
chapters (9)
- 0:00AI-driven React front ends
- 2:07Codebase drift from AI code
- 4:16Mismatched abstractions in design
- 7:05Components losing consistency
- 9:54Tests fail with AI-generated code
- 10:14Mitigations for architectural drift
- 13:23AI context limits and challenges
- 15:49Sandbox isolation for vibe coding
- 18:21AI as architecture multiplier
related talks
49mScalable Best Practices for Your Development Team
28mLessons in Managing Technical Debt
07mHow to Code Boring Internal Apps 10x Faster
43mScalable Best Practices for Your Development Team
13mDeveloping with AI: Balancing Speed and Code Quality
33mKickstarting a library of internal React components for multiple teams
43mCleaning the Tar: Using React within the Firefox Developer Tools
22mHow to introduce new technology at work (and why you maybe shouldn't)