When Humans Stop Writing Code: Rethinking Languages, Compilers, and Responsibility

Writing code is no longer the bottleneck in software development. Today, we can describe what we want in natural language and (mostly) receive entire applications in a few minutes. But while tools and demos move fast, a deeper topic largely stays behind: what happens to programming languages, compilers, and responsibility when humans stop writing the code themselves?

We have all been promised, that everything will be done autonomously when AGI is here, but what about until then … the next 3-5 years? Is your current stack/your current favorite programming language ready for real work relief professional environments?

If software is increasingly generated from intent rather than authored line-by-line, then many assumptions baked into our current languages begin to crack. Syntax stops being the primary interface. Compilers are no longer just translators. Code reviews no longer guarantee understanding. And “the AI wrote it” becomes an unacceptable answer to questions of security, correctness, and long-term maintainability.

We will explore how language design must evolve beyond syntax toward intent, constraints, and guarantees — and why this shift matters not just to developers, but especially to CTOs and tech leaders responsible for systems they may no longer fully read or write themselves. We’ll examine what responsibility means in a world of generated code, how engineering judgment changes when implementation becomes fluid, and why senior engineers become more critical—not less—in AI-native teams.

Finally, we’ll look at which existing language ideas already point in the right direction, which ones quietly break under vibe-driven development, and what a future “vibe-aware” programming language would need to get right to be trustworthy in production.

This session is an invitation to stop treating vibe coding as a novelty — and start treating it as a forcing function to rethink the core of software engineering itself.