Code generation is one of the most promising applications of large language models (LLMs), offering substantial productivity boosts for developers. However, this benefit is tempered by serious concerns surrounding the correctness and security of the generated code - especially outside the happy path.

Code generation is one of the most promising applications of large language models (LLMs), offering substantial productivity boosts for developers. However, this benefit is tempered by serious concerns surrounding the correctness and security of the generated code - especially outside the happy path.
Several solutions have been put forward to mitigate this, ranging from agentic code review to exhaustive test generation to formal verification.
In this talk, I present evidence from our research that these approaches are not currently sufficient to mitigate those concerns and instead suggest an alternative, more viable path forward based on the Scala type system.
I conclude by offering an insight from the perspective of LLM developers on why this approach is working and how even more secure coding LLMs can be developed, thanks to Scala features.
For nearly a decade, Scala's concurrency has been driven by Akka, Cats Effect and ZIO, each with its own vision for purity, safety, and pragmatism. Kyo enters this incredible ecosystem with a fresh perspective.This talk provides a critical, technical comparison of these systems through a unified framework.
Don't miss out on this opportunity to connect with Scalar community and create lasting memories!
In my talk I will argue that we can do much better by relying in a systematic way on types and capabilities.
Protobuf is commonly associated with code generation. However, in large projects with tens of thousands of message definitions, this approach can lead to an overwhelming amount of generated code. In this talk, I’ll share my journey in search of a different approach to this problem.
When writing software, we currently seem to have to choose between an imperative style - easy to read and write, hard to reason about - and a monadic style - hard to read and write, easy to reason about.This talk is about being greedy and getting the best of both worlds, because we deserve it.
I would like to present the use of NamedTuples to implement some cool things in SQL Libraries