Talk comments

Arjan Kleene at 15:05 on 28 Jan 2019

Really helpful workshop to get information about state machines and how to use them in code (which is surprisingly simple).

Robin Brackez at 14:42 on 28 Jan 2019

This is one of those few talks that contains ideas that I'll actually be able to use in real life. Good job!

Srdjan Vranac at 12:18 on 28 Jan 2019

Just a glorious evening amongst friends...

Srdjan Vranac at 12:18 on 28 Jan 2019

Incredible amount of content and information. It answered quite a few questions I had about running k8s in prod.
All of it given in a clear and understandable manner.

Srdjan Vranac at 12:16 on 28 Jan 2019

Clear, concise, explained well, good examples that were easy to understand.

Wouter Samyn at 12:15 on 28 Jan 2019

A great topic which can not get enough attention. It's too easy to forget about those basics, so a quick reminder is always useful.
The talk had great content, good code examples and was overall well structured. You didn't only focus on "how we should write code" but also took your time to explain the "why we should write it that way", which was a great asset.


TL;DR:
Great content, good presentation and a kick-ass bandshirt to rock your talk

Srdjan Vranac at 12:15 on 28 Jan 2019

This was my favorite talk of this conference, many subjects touched, many advices given.
Thank you!

Typical Jordi talk, very relaxed, almost non-chalant and based in real world experiences. Was hoping for a little more technical details.

Great talk about legacy code. One personal opinion: you said so yourself, a lot of the way we think and feel about legacy code is because of psychological reasons. In my opinion, naming something influences the way we think about it. By calling legacy code "legacy" or even "monsters", it immediately paints a negative picture of it and you're feeling bad before you're actually working on it. The fact that you're working on legacy code, probably meant it kept the business afloat for however long it has existed, so it definitely has merit.

I've once heard someone mention that because of just that, they had renamed the namespace of their legacy project to "Goldmine" as a bit of tongue-in-cheek humor. But still: it clearly indicates that, while yes, the code is old and probably a little scary, it still contains some great nuggets of knowledge.

This talk was everything it needed to be, and Frank was very correct: there have been enough theoretical talks on ES, it was time for some code.