Our colleagues Natascha, Kiwi and Martin visited the GoDays Conference 2020 in Berlin and summarized their impressions in the following blog post:

Why have you been to the GoDays?

Well, we decided to use Golang as “common tongue” for one of our biggest projects and after all, four out of five services of the project are running with it (the fifth one even exists as a prototype in Go). Well, and now, after one year of development with Go, we hoped to get new input and ideas, learn from the experiences of others and get new exciting insights at this year’s GoDays.


How was the conference?

For the GoDays a very fancy location was chosen in an old warehouse, which reminded more of a large disco than a conference location. The catering was good, albeit the rather thin coffee.

But the most important thing, the talks: the first day was not yet that relevant in terms of our project. One talk, for example, was about tracing; it was well done, but there wasn’t much new for us. But then the field report about a multiplayer game written in Go was exciting (to no surprise, well attended). Another, also interesting topic was “Internet of Gophers” with the example of a GPS tracker for dogs. We also learned that you can keep a maximum of five things in your short-term memory and should structure your code accordingly. Really exciting was the talk “Pitfalls of Observability”, where we had to find out that we should really write tests for our metrics as well; but, on the other hand, we could pat ourselves on the back for the things we already did right.


The second day of the conference started off really well. In “Fun with Functions” an example was shown which we will try out almost identically in our project code (and which looks much smarter than our current solution). Then there was a field report about a webapp in Go, where tools were reviewed that they used for it. A super exciting talk was about a deployed “Review” Kubernetes-Cluster setup, which even allows debugging and which is really handy if you run out of resources on the local machine (which, in our experience, can happen easily).

In summary, we learned something in every talk. In addition, they were all very well structured and prepared with very great care and effort (and usually with a GitHub repo). Being at my first IT conference, I was positively surprised. =)


What’s the Big Gopher Hunt?

Context: The Go Gopher is an iconic mascot and one of the most distinctive features of the Go project (aside from the language itself).

As soon as we registered, we learned that in order to get a toy gopher, we first had to collect four smiley stickers from the sponsors’ booths. It turned out that you also have to talk to the people at the booth to get the special stickers (shocker!). At RedHat the guy who was supposed to bring the stickers overslept (until noon!).

At DeliveryHero they had a nice code puzzle there (see below).

Then we found out that even with “We’re not exactly looking for a new job, but could we get a Sticker anyway?” you can get the needed stickers and also have interesting conversations. =) On the second day we could receive our gopher and cuddle it.

The riddle - What will be the Outcome?

package main

import "fmt"

type A struct {}

func (a A) Test1() string {
    return "1"

func (a *A) Test() string {
    return a.Test1()

func main() {
    var a1 A
    var a2 *A

GoDays - Do you wanna go again next year?

Yeah, definitely! Learn a lot, get new views, new ideas and technologies, and new cuddly toys! So it was worth it in every aspect!