Bend 2 and the Vibe-Coding Trap
2 hours ago
- Bend 2 requires developers to write verbose laws (58 lines) and proofs (442 lines) for simple properties, while relying on AI to generate implementations.
- The 'vibe-coding trap' occurs when developers build substantial solutions without adequate research, missing existing better approaches.
- The author of Bend appears unaware of formal verification field, as the term doesn't appear in Bend's documentation or codebase.
- SPARK, an existing formal verification language, can prove the same properties with much less code (no long proof needed) using tools like GNATprove.
- Vibe-coding can lead to implementing designs that are decades behind current state-of-the-art because LLMs don't suggest existing solutions.