Barend Linders
My first introduction to code was Fortran 90 during my (Hydro)Geology studies. It was not love at first sight. This changed when I picked up R and Python to automate some processes in my day to day job, still working in the Geology field. I noticed that the little coding projects I gave myself I found the most enjoyable, and as such, decided to jump aboard the Data train, back in 2015. Being a Data Sciencist back then was already the sexiest job, and I wanted a piece of that. I joined the NPO (Dutch public broadcaster), and have since joined Nicolab, where I currently work as a Data/Software Engineer on developing solutions to assist in the acute stroke space.
Also: come and tap me on the shoulder if you wanna talk Mountainbiking and/or Padel :-) <3.
Sessions
Our software and services often have closely linked dependencies. When writing python unit tests, one tends to mock away these dependencies (i.e. database call). Mocking - while great in some scenarios - has some drawbacks as well. At Nicolab we have embraced testcontainers for a lot of these situations. I would like to show you this tool that offers you the possibility to easily spin up your own containers representing your external dependencies and use them in your test, without ever having to leave your python / pytest environment.