GOTO Amsterdam is a vendor independent international software development conference with more that 50 top speaker and 500 attendees. The conference covers topics such as Java, Open Source, Agile, Architecture, Design, Web, Cloud, New Languages and Processes.

<< previous speaker next speaker >>

Chad Fowler, CTO at 6Wunderkinder

Chad Fowler

Biography: Chad Fowler

Chad Fowler is an internationally known software developer, trainer, manager, speaker, and musician. Over the past decade he has worked with some of the world’s largest companies and most admired software developers. Chad is CTO at 6Wunderkinder. He is co-founder and organizer of RubyConf and RailsConf and author or co-author of a number of popular software books, including Rails Recipes and The Passionate Programmer: Creating a Remarkable Career in Software Development.

Twitter: @chadfowler

Presentation: 3 SHORT TALKS: There's an App for that! Part 2

Track: There's an App for that! / Time: Thursday 11:30 - 12:20 / Location: Glazen Zaal

Mobile CI at Etsy / 11:30 - 11:45

Mobile is a strong focus at Etsy and we are working on bringing the lessons we learned from running a successful website to the mobile space. This talk will cover how we do Continuous Integration for our mobile apps and have build up an infrastructure around it that supports the workflow of mobile development.

by Daniel Schauenberg

Wunderlist: the high Volume, Multi-Master, Cross-Platform, Distributed Database System / 11:50 - 12:05

Wunderlist may look like "just a productivity app", but under the covers it's much more. It's a cross-platform, mobile, desktop, and web application with distributed database replication amongst millions of potential collaborators.
This talk will highlight some of the primary challenges and solutions in creating such a system to operate at scale.

by Chad Fowler

There should be a Service for that / 12:10 - 12:25

Persistence, error analytics, push notifications, payments, ab testing, reporting - there are many services out there to help running and operating mobile apps. At Wooga we've tried out many of them. But while these services offer good value to normal apps, they often lack support for a few critical use cases that are needed to operate mobile games at scale. We’ll talk about a few examples where Wooga ended up building its own services in the end and why.

For service providers this talk is an opinionated cry for help. For everyone else this talk is about why even good services are sometimes not good enough.

by Jesper Richter-Reichhelm

Presentation: Party Keynote: Legacy

Time: Thursday 17:10 - 18:00 / Location: Effectenbeurszaal

As software developers, we learn to abhor maintaining other people's old software. It's old, funky and brittle. In fact, we spend much of our work lives trying to kill it or at the very least marginalize its use, so we can limit our exposure to it. We pity people who have to do it.

This is what we call "legacy software".

But the word "legacy" gets a bad rap. In most other contexts, it has a positive meaning.

Maybe we're just bitter. The average life span of a software system is hardly long enough to even use the word "legacy" to describe it.

How can we turn this word around? How can we leave an actual legacy of our work as software developers?