Vibes vs Structure: What does the web dev stack of the AI era look like?

​AI is changing how we build software. But what should the stack underneath actually look like? More structure and conventions? Or just let the vibes flow?

​Do we care more about structure and guardrails that tooling brings, vs freedom and flexibility of going low level? How can we expect web dev stack to change as it adapts to serve the AI and agents better? What is the ideal DX when the main user is AI, and not human?

​Join the founders behind Wasp, ElectricSQL, Modelence, and Auto for an evening of drinks, demos, and honest conversation about what it takes to build production software in the AI era.

​What to expect:
🍻 Pizza, drinks & networking
🎬 Lightning demos from each team
🎙️ Panel: "The role of the web dev stack in the AI era"
💬 Open discussion

​Who should come:
Developers building with AI coding tools (Cursor, Claude Code, Copilot), especially in the web development space.
Web dev tooling creators.
Anybody interested in what web dev will look like in the future.

​Hosted by:
🐝 Wasp: AI-native full-stack framework aka "Rails for JS"
⚡ ElectricSQL: Real-time Postgres sync for multi-agent apps
🛠️ Modelence: Framework for vibe coding production web apps
🤖 Auto: Spec-driven AI development, made deterministic