In this article we’ll first talk about the fundamentals of retrospectives: why they are important and how to structure a simple but effective version. We’ll address a common problem: no actions and/or actors are defined. Next, we’ll take it one step further, and discuss how to avoid “getting stuck” by regularly changing the format of your retrospectives. To top it off, I offer some more varied formats.
Bye Bye, Boring RetrospectivesOn The NextBuild Conference I will host a talk about Designing scalable data intensive applications. At bol. com the datavolumes we need to process exceed the capacity of any single computer.
Nextbuild 2017Last year, a Dutch team won the Software Testing World Cup. The newly crowned Software Testing World Cup Champions were so energized by the experience they thought, “why not have a Dutch version as well?” Co-organized and hosted by...
The Dutch Software Testing ChampionshipA team of bol front-enders went to the annual React Advanced Conference and they've shared their experiences here.
Front-end Community goes to LondonCoroutines are a wonderful way of writing asynchronous, non-blocking code in Kotlin. Think of them as lightweight threads, because that’s exactly what they are. Lightweight threads aim to reduce context switching, a relatively expensive operation. Moreover, you can easily suspend and cancel them anytime. Sounds great, right?
Coroutine Gotchas - Bridging the Gap between Coroutine and Non-Coroutine WorldsIntroduction Like living organisms, companies need to learn and adapt to an ever-changing ecosystem. As a result of that, we are witnessing a paradigm shift in which domain experts are originating important innovations. They are product managers, engineers, analysts,...
Empowering autonomous experimentation in a scaling enterpriseYou are a UX researcher, and you are a UX researcher… Everybody is a UX researcher! That’s kind of our approach to user centered design at bol. com. Does it make the whole process more customer minded? Definitely.
Everybody is a UX ResearcherAt bol.com we believe Site Reliability Engineering (SRE) is the best way to balance product innovation and reliability. In essence it’s a particular set of standards, tools and practices that govern how you balance Dev and Ops in a DevOps software engineering team. But when should SRE teams be happy?
When is our SRE team successful?Senior Data Scientist Eryk plays a crucial role in developing and maintaining forecasting projects, specializing in aggregated sales. We talk to him about his journey, facing a challenging pandemic, and being part of the data scientist community at bol.
Navigating chaotic times: forecasting amid the pandemicRobin shares two things that caught his eyes in the world of Frontend
2 Things that caught my eyes in Frontend Land