With experience in building cloud-native applications at scale, Bas now focuses on Developer Experience and Platform Engineering. He designs sociotechnical systems and processes that empower engineers, streamline workflows, and reduce cognitive load to drive productivity and innovation.
In his spare time, you can find him on the tennis court. And despite having grown up in the flattest country on earth, he loves to go skiing.
It’s your first day on a new job, and you’ve been given a “quick and easy” feature to build. Shouldn’t take more than a couple of hours. At least, that’s what they said. But as you sit down, ready to dive in, the nightmare unfolds.
The onboarding guide is years out of date. Half a day disappears just setting up your local environment, only for the build to fail mysteriously on your machine.
Then comes the real fun: your feature depends on three other services, but who owns them? Where are the APIs? Slack messages go unanswered, and the internal docs might as well be written in hieroglyphs. By the time you finally write your first line of code, you’re not just frustrated, you’re drained.
This is the hidden cost of poor Developer Experience. Projects stall, innovation slows, and engineering teams struggle to deliver value.
But it doesn’t have to be this way. What if you could turn this chaos into clarity? Let’s explore how better Developer Experience isn’t just a productivity boost, it’s a game-changer for entire organizations.
Searching for speaker images...