June Meetup 2018

hosted by Tobias Pfeiffer by solarisBank AG (www.solarisbank.de), 07.06.2018 at 19:30

Join us for some great talks and nice company as well as cold drinks and some food :)

Food will be Pizza, there will be vegetarian and vegan options.

AttendAdd a Topic


Expand your leadership toolkit with “The Coaching Habit”

Ask yourself: What were your best experiences when you were coached or managed? How did the coach create a great learning experience for you that stuck with you?

In this talk I would like to share some knowledge about a book with the title "The Coaching Habit" from Michael Bungay Stanier and show you how to implement it yourself.

This talk is not just for engineering managers or coaches, but for everyone who wants to see people grow.

It's Free. It's Open. Period

Software for health and period tracking has become more and more attractive for companies to invest in. Many of these apps seem to help their users in accomplishing their goals in sports, lead a healthy life and prevent them from needing expensive health care services. However as fast as these apps appear out on the market we have no clue about their reliability and/or accuracy since most of them come without any proof or certificate.

For my master's thesis in sociology I conducted qualitative research with users of the period tracking app "Clue" in order to understand the user's motivation and needs. The vast majority of period tracking apps recently has been rated as unreliable and inaccurate by a study conducted by the German foundation "Stiftung Warentest", to which I was invited as an expert advisor.

For this talk I will share first experiences and advancements of the Bloody Health project, developing a FOSS period tracking app. With my background in both, social science and software development, I will provide interdisciplinary insights of period and health tracking from different angles.

JSON API — A specification for building APIs in JSON

I've been planning to give this as an internal talk, since we (at DaWanda) started to use json:api for our new internal services.

My current idea about the structure is like this:

  • (some) problem statements with current APIs
  • intro to the json:api specifications
  • implementation in Ruby (on Rails)
  • a bit about my own experience with it so far

Is anybody out there, who would also be interested in hearing more about this?

Attendees: (51)


Become a patron
Fork me on GitHub!