Tools and infrastructure for hackable projects

At Google we like the concept of "hackability", which means that a product is easy to hack on. This means the tools and build systems should be fast, the product should be easy to run and debug on your workstation (even if it's servers or JNI in Android apps!), and it should be well covered by tests. We're going to talk about how you can get your developers to write tests and reduce their frustration. We'll also talk about how we set up our build bots in Chrome, and give some practical tips around that

Speakers

Patrik Höglund: I'm a Software Engineer, Tools & Infrastructure (SETI) at Google, and I've been with Google for four years. I've always cared deeply about code quality, design, architecture and testing, and shipping quality products with well-written, clean code. Since the beginning I've been working on the WebRTC project, which aims to build a new foundation for communication between people. The project is based on the open-source www.webrtc.org (http://www.webrtc.org/) codebase. WebRTC now powers Hangouts, Facebook Messenger, Snapchat and other big communication products.

Henrik Kjellander: I've been a Test Engineer (TE) at Google for four years. I like engineering productivity and product excellence and believe that in order to achieve that; you have to provide the right tools and a development process that fits the team. Important ingredients are: modern build systems and source control, code reviews, pre-commit testing, performance measurements and effective bug handling. Like Patrik I'm working in the WebRTC team and spend most of my time on build- and development infrastructure and test planning.