EuroSciPy 2017

The EuroScipy 2017 took place in Erlangen, Germany. It was fist developer conference ever that I attended. In the following I want to briefly describe my expierence, followed by some fan pics and a few take aways at the end.

Conference overview

The program to the conference can be found here.
Every talk was recorded and uploaded on Youtube.

On the first two days there were only tutorials. They had a beginner track and an advanced track. I switched back and forth between the two (see program link).

Julia Rohrer gave the keynote “How to Fix a Scientific Culture: Psychology as a Cautionary Tale and Paragon” of the conference. I didn’t expect the scientific culture to bad that bad. She talked about p-hacking (= use of creative methods to make the outcome of your experiment statistical significant) and how the current system of grant distribution causes bad behavior among scientist.

Talks I liked

Meeting scipy core developers

Tim Head (@betatim) is a core contributor to scikit-optimize.
He gave a very informative talk about Bayesian Optimization. As Tim also enjoys running, we went for a run together in the morning of the second day. 01

Olivier Grisel (@ogrisel) is contributor to scikit-learn.
Olivier is a really funny guy and thus quite approachable. He publishes most of his tutorials on github which are very helpful. 02

Joris Van den Bossche (github) is a core contributor to pandas.
He sat down with me for a couple of minutes to give me some tips ron how to solve an optimization problem for a site project. 03

Soumith Chintala (@soumithchintala is a core contributor to PyTorch.

Take aways from a first timer

  1. Bring your own problems (side projects, academic projects, …)
    People tend to enjoy discussing a concrete problem much more than a broad question which you could google anyway.
  2. Don’t focus too much on the talks
    All the talks will be recorded and uploded but the people will be gone. If you get along with a person really well, I think it’s not a bad idea to skip a talk entirely.
  3. Prepare questions beforehand
    Sometimes I was just overwhelmed by the talk and was afraid to ask silly questions. That’s why it’s a good idea to spend some minutes with the material before the conference.


My high expectations were satisfied. I didn’t know anybody when I arrived and left with some new friends. The conference helped me to get a much better understanding of the scientific programming ecosystem in Python. The conference also helped me to get an idea whether I would enjoy working as a software developer or not.

comments powered by Disqus