Yael Bakker
Software Engineer @ Info Support
Software Engineer @ Info Support
Veenendaal, The Netherlands
Actions
Yael Bakker is a software engineer at Info Support with a focus on maintainable systems, developer experience and open source. He’s also a Judo black belt and a (coffee) geek: always in pursuit of balance, clarity, and the perfect brew.
He enjoys learning new tricks, especially through sharing them with others.
Yael Bakker is een software engineer bij Info Support, met passie voor onderhoudbare software, developer experience en open source projecten. Je kunt met hem altijd een praatje aangaan over koffie, martial arts of andere geek-outs.
Yael is altijd op zoek naar nieuwe dingen om te leren, en verdiept graag zijn kennis door deze onderwerpen weer met anderen te delen.
Area of Expertise
Topics
Your tests as prompts: How BDD complements AI augmented development en
AI augmented development delivers fast, but only speed and no shared understanding will just produce the wrong code faster. Rising token costs make building the same thing over and over again, less than desirable. Behavior Driven Development already offers a useful counterbalance: clear, example-driven scenarios, written in natural language that describe what the system should actually do.
In this talk, we’ll explore how BDD and Cucumber can work hand-in-hand with an AI-augmented development workflow. Scenarios written in Gherkin are readable by product owners, testers, developers, and increasingly, AI tools. That makes them a valuable source of context: they describe intent, capture edge cases, and provide a feedback loop when generated or modified code does not match expectations.
We’ll discuss how BDD scenarios can serve as living documentation, acceptance criteria, regression tests, and structured prompts for AI-assisted coding. We’ll also go over practical examples for the .NET ecosystem, lessons learned, meaningful boundaries, and avoiding implementation detail.
This session is for developers, testers, and teams experimenting with AI-assisted development who want to take the next step. You’ll learn how BDD can help keep AI-generated code grounded in behavior, collaboration, and shared intent.
Turning people into cards: behind the scenes nl
We wanted to turn people into trading cards. So we built it.
In deze talk nemen Willem Meints en Yael Bakker je mee achter de schermen van onze open source trading card generator: een applicatie die (conferentie)bezoekers omtovert tot gepersonaliseerde kaarten.
We laten zien hoe het werkt: van het genereren van pakkende thema’s tot het omgaan met sterk variërende inputdata (niets is zo random als mensen), en welke technische keuzes daarbij een rol speelden. Natuurlijk delen we ook de uitdagingen die we tegenkwamen tijdens het ontwikkelen, testen en vooral het gebruik in de praktijk (waar alles altijd nét even anders loopt dan verwacht).
Verwacht concrete lessons learned, nerdy details, en een blik op wat er nog komt. Want als je eenmaal begint met mensen in kaarten veranderen… wil je daar eigenlijk niet meer mee stoppen.
Save your tokens: use source generators! en
AI augmented development makes it easier than ever to generate code, but that does not mean it has become free. Every repeated prompt consumes context, and is non deterministic. Every generated variant needs review, and every inconsistency becomes future maintenance. For repeatable patterns, C# source generators offer a different approach: codify once and let the compiler produce the code for you.
In this talk, we’ll explore how to build practical source generators that solve real world problems, not just hello world examples. We’ll look at where source generators fit, how they work, and how they can reduce boilerplate for tasks such as mapping, registration, serialization support, strongly typed accessors, or repetitive glue code.
We’ll focus on the trade-offs that matter in production: keeping generated code understandable, designing a useful developer experience, debugging generator output, avoiding over-engineering, and deciding when a generator is worth the investment. Along the way, we’ll connect this to AI-augmented development: when should you ask an agent to generate code? And when should you turn the pattern into a tool? Of course we'll use AI augmented development to manufacture the actual generators, it's 2026, duh!
Why the agent doesn't fall far from the tree: make your life easier with git worktrees en
Do you ever find yourself waiting for your agent(s), only wishing you could tick another item off your ever growing backlog in the meantime? Want to review your colleague's work but you're in the middle of important changes? Don't want to git stash, wip commit or clone your repo ten times over? Meet git Worktrees! Perhaps you've heard of these: they're wildly used by Claude Code, VScode Agents view and many more. For sure we'll dive into why this is, what they are and how they work. However, also, perhaps like me, you find these tools (too) opinionated or are restricted in their use. What if you want the power of worktrees but manual? In this talk I'll show you how you can get started with git worktrees yourself, without the headaches.
ISKS 2026 - Built to last Sessionize Event
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top