Amsterdam
Upcoming
When AI does the easy work, humans get the hard parts. As machines handle routine cases, people inherit the ambiguous ones: deciding whether an answer is actually right, and practicing less of the skills the system now does. This talk looks at what happens to human judgment, expertise, and decision-making when machines increasingly do the thinking with us.
Upcoming
Software engineers know that every system carries the weight of past decisions. The human mind is no different. We all run beliefs, habits, and reactions that were written years ago, often for problems that no longer exist.
Upcoming
Software engineers are trained to find answers and reach a conclusion. This talk is about what happens when confidence becomes certainty, and certainty stops the questions.
Upcoming
Software engineers know that every system carries the weight of past decisions. The human mind is no different. We all run beliefs, habits, and reactions that were written years ago, often for problems that no longer exist.
Hosted
An afternoon of practical talks, debate, and hands-on learning for product teams, hosted with Steven Roest from ING.
Given
We like to think our decisions are logical, but they often are not. Cognitive biases can trick us into choosing the wrong solution, underestimating complexity, or overestimating our abilities.
Given
Software engineers know that every system carries the weight of past decisions. The human mind is no different. We all run beliefs, habits, and reactions that were written years ago, often for problems that no longer exist.
Given
A conversation on where API strategy is heading: how far APIs and AI will converge, deterministic versus probabilistic approaches, and the skills teams will need.
Given
Software engineers know that every system carries the weight of past decisions. The human mind is no different. We all run beliefs, habits, and reactions that were written years ago, often for problems that no longer exist.
Given
Modern frontend teams often rely on powerful UI frameworks to move fast, but over time those tools can quietly become bottlenecks. This is the story of leaving MUI and rebuilding the component library with CSS and CSS Modules.
What happens to judgment when someone agrees with a model too quickly.
Whether a model can already carry a bias before a person agrees with it.
The work that remains after an AI produces a usable piece of code.
After an incident, asking what happened instead of who caused it.
Five changes that cut a slow, flaky Playwright suite roughly in half.
Moving one frontend from Craco, tsup, tsdx, and tsx onto Vite.
A first-day letter for someone joining epilot.
A short note on the part of the brain that chooses the harder task.
Cognitive biases that show up in how developers estimate work.
Ten habits that get in the way of seeing a system as a whole.
Checks for keeping a React application's performance steady day to day.
Three from my LinkedIn. Click one and it plays here.
Before moving into software, I spent five years in cartography and geodesy, followed by five years as a fashion photographer. I also studied land-use planning and translation. These different paths have given me a lasting curiosity about how things fit together, how complex systems work, and how to make complicated ideas easier to understand.
Outside of work, I'm fascinated by cognitive science and quantum physics, and I'm still drawn to the intersection of technology, science, and art.
I mentor on ADPList. I work in English, speak Dutch at an intermediate level, and am eligible to work across the EU.
I was preparing for frontend developer job interviews with Kate. She explains difficult things in a simple way, pays attention to details, and always supports you during the preparation process.
Kate and I collaborated closely on a major, high-stakes project soon after I joined, where I witnessed her exceptional technical depth and reliability. From the moment I joined the team, she made me feel welcome and helped me to integrate properly.