Room 2

13:40 - 14:40 (UTC+02)

Talk (60 min)

Lightning Talks

Lightning talks (approx 10-15 minutes each)


Talk 1: Look ma, no hands! - How to program without using your hands - Peder Voldnes Langdal

Have you ever wondered how to answer an email, surf online, or even program without using your hands? Probably not, but did you just become a bit curious? Due to a juicy inflammation in my elbow I had to find the answers to these questions, and now I want to show you what I learnt. I will show you voice commands, voice coding and eye tracking, and use these to create a simple little web app on stage. You do not need to know programming to enjoy this talk. P.S: This text is written without a mouse and keyboard.


Talk 2: How to Manage your Ducks: Being a More Sustainable You - Amy Kapernick

Ever feel like everything's a struggle? Like you're constantly overwhelmed by life? While we can endure it and pull through, this is hardly sustainable. Sometimes, it's just too ducking hard.

We've all been there. Thankfully, there are simple things you can do to not only reduce the stress factors, but sometimes eliminate them altogether.

Join me to learn about setting (and sticking) to your boundaries, identifying which worries help and which ones harm, and most importantly, how to manage your ducks. These are personally vetted, tried and tested steps for being a more sustainable you.


Talk 3: Death to Test Environments - Nikolai Norman Andersen

A validated, stable and usable environment to execute test scenarios and replicate bugs, or a wasteful effort that will never be able to replicate production data or usage patterns? Have the use of test environments gone to far, or are we just doing it wrong? Let's have a look at some normal ways of utilizing test environments and some changes we can do to get more value out of them. Maybe we'll decide we don't need one at all!


Talk 4: Betting the company on Clojure - Erik Assum

When Erik Bakstad and Magnulf Pilskog founded Ardoq in 2013, they decided to use Clojure to implement the backend, and Javascript for the frontend. Now almost 10 years later, Ardoq is a successful scale up with over 200 employees. In this lightning talk we'll examine the reasons for choosing Clojure, and how those decisions turned out. We will also compare our experiences working both in working in the code base and how easy it has been to hire new employees.

Peder Voldnes Langdal

I have worked for 5 years as a software consultant for big, governmental organizations. I am motivated by knowing that the software I create is needed by the users, and I therefore love talking to my users. In my spare time I like to climb, ski, or watch cooking shows. Also I have published exactly one paper, which I am overly proud of.

Amy Kapernick

Amy wears many hats as a freelance developer, business owner and conference addict. She regularly shares her knowledge with her peers and the next generation of developers by mentoring, coaching, teaching and feeding into the tech community in many ways.

Amy can be found volunteering her time with Fenders, ACS, SheCodes (formerly Perth Web Girls) and MusesJS (formerly NodeGirls). She also works as an evangelist for YOW! Conferences, is a Twilio Champion, Microsoft MVP and has been nominated for the WiTWA awards for the last 2 years.

In her spare time Amy shares her knowledge and experience on her blogs and speaking at conferences. She has previously given keynotes at multiple events as well as speaking at several international conferences in the US and Europe.

Nikolai Norman Andersen

Nikolai specializes in how processes and technology work together to enable continuous delivery of solutions. He is always searching for ways to deliver fast without compromising quality. He loves problems related to distributed systems, automation and infrastructure, but shines when focusing on developer experience and deployment pipelines.

Erik Assum

Erik is a wearer of many hats at Ardoq, a Norwegian scale up in the enterprise architecture space . He’s a mainly a backend programmer, but tends to work wherever the code is bad enough. Given time he’ll eventually drift into some sort of devops role while trying to figure out how to run the current project even better.

Lately, he's been lurking around open-source Clojure projects looking for easy bugs to fix. This is his way of paying back to the community.