Date & time
17:00
Register for the panel discussion
Login or join LeadDev.com to view this content
Two words that will send a shiver down the spine of any engineering leader: vibe code. But it doesn’t have to be that way. Developers keen to experiment with AI-generated code can lean on tried and tested experimentation tools to safely test multiple feature ideas all at once.
The promise of faster prototyping is clear for even experienced developers when it comes to vibe coding, but the risks are also very real, even to the trained eye. Recent reports of Microsoft’s EchoLeak flaw, GitHub Copilot’s caching leaks, and hacked vibe-coded applications all show what can happen when the vibes turn bad.
Join this expert panel to discuss how vibe coding doesn’t need to be a dirty word, and the best guardrails to set to make the output production-ready:
Register to learn:
- Security non-negotiables when vibe coding
- The role of feature flags and testing when experimenting with AI-generated code
- Tactics for moving AI-generated code into production faster and safer