Explore Presentations

Precision vs. Prediction: The Trouble With LLMs and Libraries

Abstract

Libraries and frameworks are where LLMs often break down: too much context, too many moving parts, and lots of hidden assumptions. In this talk, we’ll unpack why models struggle in this space and present our method for structuring library knowledge into digestible chunks. Using Svelte as the running example, you’ll see what goes wrong when models get it wrong, and how Tessl's approach can help them finally get it right.

Overview

Why frameworks and libraries trip up LLMs

Software engineering, among other things, requires precision in language, API patterns, and dependency versioning. But models are trained on snapshots of data that:

  • Are taken in the past, meaning they have no knowledge of a framework just released;
  • Contain mixed and sometimes contradictory information about the same package. For example, different versions without clear differentiation;
  • Provide an unbalanced distribution of information. Some packages are well-documented, while others have very little coverage.

We’ll unpack why this matters for developers relying on AI coding tools and introduce a practical tool to help.

Tessl's method

  • Structured, doc-like blueprints of a package’s API, best practices, and examples.
  • They give coding agents a reliable reference point while iterating, helping them stay aligned with how a library is really meant to be used.

Svelte as a running example

  • Svelte poses a particular challenge: LLMs often mix it up with other frameworks or fall back to using older Svelte versions patterns.
  • With our method, the same agent can navigate the framework more effectively, producing cleaner, more accurate code.
Maria Gorinova

Inside Erlang Battleground: A Conversation with Brujo Benavides

A conversation with Brujo Benavides at the SE4FP Warm-up.

Brujo is an Erlang developer and trainer. He currently works as a Senior Erlang Engineer at Baxter. He has organized events such as SpawnFest and ElixirConf LA. He lives in Sant Cugat del Vallès, Spain.

Education: Computer Science, University of Buenos Aires (UBA).

Website: https://about.me/elbrujohalcon

Brujo is the creator of Erlang Battleground, a collection of funny and weird stories discovered while coding in Erlang.
Read more: https://medium.com/erlang-battleground

This session is also part of Adolfo Neto's Introduction to Functional Programming course, offered annually at PPGCA, UTFPR's Professional Master’s Program in Applied Computing. Today’s guest previously joined that course for an interview in an earlier edition of this course: https://www.youtube.com/watch?v=6MTSl2OArd0

Fill out https://forms.gle/J88PVbxiSew1bKeo6 if you want to be notified about future talks. The schedule is already available at https://se4fp.github.io/2025/#esquenta

Brujo Benavides

Vike: Modular React Framework

React frameworks like Next.js and Remix restrict and dictate your stack in ways they shouldn't.

Vike is a (React) framework designed from the ground up to be modular:

  • Choose your architecture: SPA/SSR/SSG, RPC/GraphQL/REST, server/static/edge deployment, ...
  • Use tools with zero-config integration (Vike extensions) or fully control integration code.

Vike embraces the do-one-thing-do-it-well philosophy for unprecedented flexibility and stability. For example, if you have an existing backend with a GraphQL API, then you don't need Server Actions. With Vike, you can use React your way — such as first-class support for GraphQL instead of Server Actions.

Your stack, your choice.

Rom Brillout

Precision vs. Prediction: The Trouble With LLMs and Libraries

Abstract

Libraries and frameworks are where LLMs often break down: too much context, too many moving parts, and lots of hidden assumptions. In this talk, we’ll unpack why models struggle in this space and present our method for structuring library knowledge into digestible chunks. Using Svelte as the running example, you’ll see what goes wrong when models get it wrong, and how Tessl's approach can help them finally get it right.

Overview

Why frameworks and libraries trip up LLMs

Software engineering, among other things, requires precision in language, API patterns, and dependency versioning. But models are trained on snapshots of data that:

  • Are taken in the past, meaning they have no knowledge of a framework just released;
  • Contain mixed and sometimes contradictory information about the same package. For example, different versions without clear differentiation;
  • Provide an unbalanced distribution of information. Some packages are well-documented, while others have very little coverage.

We’ll unpack why this matters for developers relying on AI coding tools and introduce a practical tool to help.

Tessl's method

  • Structured, doc-like blueprints of a package’s API, best practices, and examples.
  • They give coding agents a reliable reference point while iterating, helping them stay aligned with how a library is really meant to be used.

Svelte as a running example

  • Svelte poses a particular challenge: LLMs often mix it up with other frameworks or fall back to using older Svelte versions patterns.
  • With our method, the same agent can navigate the framework more effectively, producing cleaner, more accurate code.
Maria Gorinova

Inside Erlang Battleground: A Conversation with Brujo Benavides

A conversation with Brujo Benavides at the SE4FP Warm-up.

Brujo is an Erlang developer and trainer. He currently works as a Senior Erlang Engineer at Baxter. He has organized events such as SpawnFest and ElixirConf LA. He lives in Sant Cugat del Vallès, Spain.

Education: Computer Science, University of Buenos Aires (UBA).

Website: https://about.me/elbrujohalcon

Brujo is the creator of Erlang Battleground, a collection of funny and weird stories discovered while coding in Erlang.
Read more: https://medium.com/erlang-battleground

This session is also part of Adolfo Neto's Introduction to Functional Programming course, offered annually at PPGCA, UTFPR's Professional Master’s Program in Applied Computing. Today’s guest previously joined that course for an interview in an earlier edition of this course: https://www.youtube.com/watch?v=6MTSl2OArd0

Fill out https://forms.gle/J88PVbxiSew1bKeo6 if you want to be notified about future talks. The schedule is already available at https://se4fp.github.io/2025/#esquenta

Brujo Benavides

Vike: Modular React Framework

React frameworks like Next.js and Remix restrict and dictate your stack in ways they shouldn't.

Vike is a (React) framework designed from the ground up to be modular:

  • Choose your architecture: SPA/SSR/SSG, RPC/GraphQL/REST, server/static/edge deployment, ...
  • Use tools with zero-config integration (Vike extensions) or fully control integration code.

Vike embraces the do-one-thing-do-it-well philosophy for unprecedented flexibility and stability. For example, if you have an existing backend with a GraphQL API, then you don't need Server Actions. With Vike, you can use React your way — such as first-class support for GraphQL instead of Server Actions.

Your stack, your choice.

Rom Brillout

Precision vs. Prediction: The Trouble With LLMs and Libraries

Abstract

Libraries and frameworks are where LLMs often break down: too much context, too many moving parts, and lots of hidden assumptions. In this talk, we’ll unpack why models struggle in this space and present our method for structuring library knowledge into digestible chunks. Using Svelte as the running example, you’ll see what goes wrong when models get it wrong, and how Tessl's approach can help them finally get it right.

Overview

Why frameworks and libraries trip up LLMs

Software engineering, among other things, requires precision in language, API patterns, and dependency versioning. But models are trained on snapshots of data that:

  • Are taken in the past, meaning they have no knowledge of a framework just released;
  • Contain mixed and sometimes contradictory information about the same package. For example, different versions without clear differentiation;
  • Provide an unbalanced distribution of information. Some packages are well-documented, while others have very little coverage.

We’ll unpack why this matters for developers relying on AI coding tools and introduce a practical tool to help.

Tessl's method

  • Structured, doc-like blueprints of a package’s API, best practices, and examples.
  • They give coding agents a reliable reference point while iterating, helping them stay aligned with how a library is really meant to be used.

Svelte as a running example

  • Svelte poses a particular challenge: LLMs often mix it up with other frameworks or fall back to using older Svelte versions patterns.
  • With our method, the same agent can navigate the framework more effectively, producing cleaner, more accurate code.
Maria Gorinova

Inside Erlang Battleground: A Conversation with Brujo Benavides

A conversation with Brujo Benavides at the SE4FP Warm-up.

Brujo is an Erlang developer and trainer. He currently works as a Senior Erlang Engineer at Baxter. He has organized events such as SpawnFest and ElixirConf LA. He lives in Sant Cugat del Vallès, Spain.

Education: Computer Science, University of Buenos Aires (UBA).

Website: https://about.me/elbrujohalcon

Brujo is the creator of Erlang Battleground, a collection of funny and weird stories discovered while coding in Erlang.
Read more: https://medium.com/erlang-battleground

This session is also part of Adolfo Neto's Introduction to Functional Programming course, offered annually at PPGCA, UTFPR's Professional Master’s Program in Applied Computing. Today’s guest previously joined that course for an interview in an earlier edition of this course: https://www.youtube.com/watch?v=6MTSl2OArd0

Fill out https://forms.gle/J88PVbxiSew1bKeo6 if you want to be notified about future talks. The schedule is already available at https://se4fp.github.io/2025/#esquenta

Brujo Benavides

Vike: Modular React Framework

React frameworks like Next.js and Remix restrict and dictate your stack in ways they shouldn't.

Vike is a (React) framework designed from the ground up to be modular:

  • Choose your architecture: SPA/SSR/SSG, RPC/GraphQL/REST, server/static/edge deployment, ...
  • Use tools with zero-config integration (Vike extensions) or fully control integration code.

Vike embraces the do-one-thing-do-it-well philosophy for unprecedented flexibility and stability. For example, if you have an existing backend with a GraphQL API, then you don't need Server Actions. With Vike, you can use React your way — such as first-class support for GraphQL instead of Server Actions.

Your stack, your choice.

Rom Brillout

Precision vs. Prediction: The Trouble With LLMs and Libraries

Abstract

Libraries and frameworks are where LLMs often break down: too much context, too many moving parts, and lots of hidden assumptions. In this talk, we’ll unpack why models struggle in this space and present our method for structuring library knowledge into digestible chunks. Using Svelte as the running example, you’ll see what goes wrong when models get it wrong, and how Tessl's approach can help them finally get it right.

Overview

Why frameworks and libraries trip up LLMs

Software engineering, among other things, requires precision in language, API patterns, and dependency versioning. But models are trained on snapshots of data that:

  • Are taken in the past, meaning they have no knowledge of a framework just released;
  • Contain mixed and sometimes contradictory information about the same package. For example, different versions without clear differentiation;
  • Provide an unbalanced distribution of information. Some packages are well-documented, while others have very little coverage.

We’ll unpack why this matters for developers relying on AI coding tools and introduce a practical tool to help.

Tessl's method

  • Structured, doc-like blueprints of a package’s API, best practices, and examples.
  • They give coding agents a reliable reference point while iterating, helping them stay aligned with how a library is really meant to be used.

Svelte as a running example

  • Svelte poses a particular challenge: LLMs often mix it up with other frameworks or fall back to using older Svelte versions patterns.
  • With our method, the same agent can navigate the framework more effectively, producing cleaner, more accurate code.
Maria Gorinova

Inside Erlang Battleground: A Conversation with Brujo Benavides

A conversation with Brujo Benavides at the SE4FP Warm-up.

Brujo is an Erlang developer and trainer. He currently works as a Senior Erlang Engineer at Baxter. He has organized events such as SpawnFest and ElixirConf LA. He lives in Sant Cugat del Vallès, Spain.

Education: Computer Science, University of Buenos Aires (UBA).

Website: https://about.me/elbrujohalcon

Brujo is the creator of Erlang Battleground, a collection of funny and weird stories discovered while coding in Erlang.
Read more: https://medium.com/erlang-battleground

This session is also part of Adolfo Neto's Introduction to Functional Programming course, offered annually at PPGCA, UTFPR's Professional Master’s Program in Applied Computing. Today’s guest previously joined that course for an interview in an earlier edition of this course: https://www.youtube.com/watch?v=6MTSl2OArd0

Fill out https://forms.gle/J88PVbxiSew1bKeo6 if you want to be notified about future talks. The schedule is already available at https://se4fp.github.io/2025/#esquenta

Brujo Benavides

Vike: Modular React Framework

React frameworks like Next.js and Remix restrict and dictate your stack in ways they shouldn't.

Vike is a (React) framework designed from the ground up to be modular:

  • Choose your architecture: SPA/SSR/SSG, RPC/GraphQL/REST, server/static/edge deployment, ...
  • Use tools with zero-config integration (Vike extensions) or fully control integration code.

Vike embraces the do-one-thing-do-it-well philosophy for unprecedented flexibility and stability. For example, if you have an existing backend with a GraphQL API, then you don't need Server Actions. With Vike, you can use React your way — such as first-class support for GraphQL instead of Server Actions.

Your stack, your choice.

Rom Brillout

Ultra-low latency SvelteKit

Recently, I did a demo of a 3D engine at 120fps which caught the eye of Googler Jason Mayes at CityJS Athens, May 2025 – but how do we introduce multiplayer without killing the UX?

Primary Photo for Scott PhillipsScott Phillips

Guild

Get in touch!

hi@guild.host