Does your team have boring retrospectives? Do you learn from these meetings or do they drain energy? A good retrospective is a powerful tool for your team. In this podcast episode, you learn more about how to get your retrospective fun, fast and fruitful.
At bol.com we like our teams to be autonomous when it comes to implementing solutions to help our customers. However if people are completely free to do whatever they want to reach a team goal we might end up in the bottom right corner of the picture due to lack of direction. We like to be in the upper right corner where there’s both freedom and alignment. The other parts of the diagram are of course less desirable for our software engineers and data scientists.
With 2 of our engineers, we look into how we keep enhancing the quality of our webshop using canary testing and analysis, contract testing and end-to-end testing in isolation.
June 2022 - We celebrated Tech Culture Month at bol.com. Together with the initiators and organizers, we discuss the ins- and outs of this series of events.
During this month, the Tech Culture Manifesto was introduced. We explore what this manifesto is about, how it got on paper and what we aim for with it.
If you’re performing web requests with Spring Boot’s WebClient you perhaps, just like us, read that defining the URL of your request should be done using a URI builder
Demo-time; Google Glass capabilities in a pop-up Warehouse
Testing the boundaries of the technology that we have today and having the opportunity to put a Google Glass on and experience operating in a pop-up Warehouse. Those were the results of a joint experiment by Google and bol.com.
With software engineers of both Xebia and bol.com, we discuss the introduction of a language like Go in an organisation. We check its readability and simplicity and find ways to onboard engineers in the Go experience.
How to prevent common performance defects with the jPinpoint PMD rules
Prevention is better than cure - a fundamental principle of health care that also applies to modern software development. The later a bug surfaces, the more effort it takes to repair. From our own experience we know that this especially applies to performance bugs.