17 hours ago
- Not every change made by an LLM warrants the same level of scrutiny; low-risk edits like button copy or UI relocation need only basic smoke tests.
- High-risk code changes involving authentication, permissions, payments, user data, infrastructure, or destructive operations require slowing down, reading surrounding code, and testing failure paths.
- The key mistake is treating all tasks equally in terms of danger; low-risk work needs simple verification, while high-risk work demands deep comprehension and care.
- Where mistakes are cheap, let LLMs work freely; where consequences are serious, actively engage to ensure correctness.