Please log in to watch this conference skillscast.
Your responsibility as developers is to ship high quality features in a timely manner. But there are many factors which can hinder development: from tightly coupled, untested codebases, to differences between team members in architecture visions and API knowledge, to time pressure. So, given all of these, how do you ensure that we’re making the right amount of compromises? In this Keynote talk, Florina is going to share with you some of the lessons she learned along the way and show how she applied them in rewriting Plaid. You'll learn how important it was to set a goal for the architecture, to create a common language in the team, to adopt technologies for the right reasons and to avoid premature optimisation.
YOU MAY ALSO LIKE:
Keynote: Pragmatic Crafting
Florina is working as an Android Developer Advocate at Google, helping developers architect clean, testable apps using the Architecture Components libraries. She has been working with Android for 8 years, previous work covering news at upday, payment solutions at payleven and navigation services at Garmin.