RUG::B

Ever noticed how many (seemingly simple) idioms exist in the world of code-writing that explain (fairly complex) concepts/ situations/ problems?
On one hand it's practical because you save time explaining things because there is already a word or expression for it.
On the other hand it can cause confusion because not everybody might be familiar with the terms (think beginners or developers from other language communities).
I want to show you my top 10 (maybe more?) of these expressions, bundled up in The Programmer's Glossary. What is behind these expressions? What's their backstory? Do they have anything to do with computer at all? Let's find out!
This is a more or less entertaining talk with (maybe) audience involvement.

Fun Fact: I first wanted to title this talk 'The Programmer's Zoo' because a lot of expressions involve animals. But not all of them :sad_panda:

Note: I can give this November 2016 at the earliest.

As developers we care a lot about metrics and benchmarks related to our code and its speed. You know how to improve the test coverage or how to make this one request faster. But how do you improve your conversion rate, how can you validate if a feature was a success?

In this talk I will tell about my own journey from low motivation to AB-Testing and how small measurements can keep you happy. I will give you an introduction about the statistical background of AB Testing and some best practices you can easily apply.

With components your apps will be happier, healthier, and development will be more fun. Let me show you how!

Components add a layer of structure that is not present in many applications. The structure in question is that of bounded contexts. Bounded contexts with boundaries enforced and tests separated. If you have thought that your app is too big and that the way to save it is micro services, you may want to take it one step slower and look at components first. In Ruby, we create component-based apps with gems; in Rails, we add engines.

The technology is one thing - there is a lot to consider there. This talk will quickly cover the tech and dive deeper into the what, the why, and how of component-based application development.