From Vibe Coding to AI-Enabled Engineering
- Date
- 2026-06-09
- Location
- London, England, United Kingdom
- Host
- Personal
About this event
Software is changing fast. What started as quick prompts and "vibe coding" experiments is becoming something much more serious: a new style of engineering where AI helps write, test, review, and even shape how products get built. This event is for people who want to move beyond the hype and get clear on what AI-enabled engineering actually looks like in practice, where it works, and what good teams need to think about next. About the Event From Vibe Coding to AI-Enabled Engineering is an in-person gathering in London for people thinking seriously about the future of building software with AI. The title says a lot: this is about the shift from casual experimentation to more deliberate, reliable, and scalable ways of working. Some people are already using AI as a fast drafting tool. Others are exploring agentic workflows, autonomy, and new ways to structure engineering teams. This event creates space to talk about that transition clearly and honestly, with a community of people who are actively building, questioning, and learning. Expect a format that feels practical and grounded rather than abstract. The focus is on how AI is changing coding and engineering work at multiple levels: individual productivity, team process, system quality, and the relationship between speed and responsibility. This is also a community event, which matters. The best conversations around AI and engineering usually happen when ambitious technical people compare notes openly: what is working, what feels fragile, what is overhyped, and what is already becoming normal. What to Expect You can expect a focused evening built around discussion, shared perspectives, and practical insight into the current state of AI in software development. Rather than treating AI as a novelty, the event centers on how engineering practice evolves when these tools become part of the stack. Topics likely to shape the conversation include: The difference between fast, intuitive "vibe coding" and robust engineering Where autonomy helps and where human judgment is still essential How AI changes coding workflows, reviews, debugging, and iteration speed The emerging habits and safeguards that make AI-assisted work more dependable What individuals and teams need to learn to stay effective as tooling improves There will also be value in the room itself. In-person events create a different level of exchange than a comment thread or online panel. You can ask sharper questions, pressure-test your assumptions, and hear how others are approaching similar problems from different angles. If you are experimenting with AI tools already, this is a chance to put your experience in context. If you are still working out how seriously to take the shift, this event will help you get more specific about the opportunities and tradeoffs. Why Attend The biggest reason to attend is clarity. AI in engineering is full of strong opinions, but not enough useful distinctions. This event is designed for people who want to separate signal from noise and understand what changes when AI moves from a side tool to a meaningful part of the engineering workflow. You should leave with a better sense of the current landscape: not just what tools can do, but how to think about quality, autonomy, speed, trust, and accountability when AI is involved. That perspective is useful whether you write code every day, lead technical work, or shape product and engineering decisions. There is also a career reason to be in the room. The way strong engineers work is changing, and the people who adapt early will be better positioned to build, lead, and collaborate well in this next phase. Understanding AI-enabled engineering now is not about chasing novelty; it is about keeping your technical judgment sharp as the ground shifts. You may also meet people wrestling with the same questions you are. That could mean comparing workflows, challenging assumptions, or finding collaborators who care about building thoughtfully in an AI-heavy environment. Good community events do more than inform; they help people orient themselves together. Practical Details This event takes place in person in London, United Kingdom on Tuesday, June 9 at 5:00 PM GMT+1. The in-person format makes it especially well suited to nuanced technical discussion, candid questions, and the kind of back-and-forth that helps ideas become more concrete. Because the topic spans AI, coding, autonomy, tech, and community, attendees are likely to come from a mix of backgrounds across software and product work. You do not need to fit a narrow profile to get value here, but you should be ready for a conversation that assumes genuine interest in how engineering is evolving. A few useful ways to prepare: Come with examples from your own workflow if you have been using AI tools Bring questions about where current tools succeed or fail in real engineering contexts Be ready to talk about tradeoffs, not just capabilities Expect thoughtful discussion rather than surface-level takes If you care about where software development is heading, this is the kind of event that can sharpen your thinking quickly. London is the meeting point, but the real draw is the chance to discuss one of the most important shifts in modern engineering with other people taking it seriously.
Who should attend
This is for people who want a more precise, grounded view of how AI is changing software work, and who are curious enough to question both the hype and the old assumptions. - You write code and want to understand how AI can improve your workflow without lowering standards. - You are an engineer, technical lead, or manager thinking about what autonomy, AI assistance, and faster iteration mean for real team practices. - You have experimented with coding tools, copilots, or agent-style workflows and want to compare notes with others doing the same. - You are trying to figure out the difference between quick prototype energy and durable engineering discipline. - You work close to engineering in product, developer tools, or technical operations and want a better mental model for where this is heading. - You value thoughtful in-person discussion and would rather explore practical tradeoffs with a strong community than consume another generic AI hot take online.