<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ernesto Carrión</title>
    <description/>
    <link>https://speakerdeck.com/ecarrion</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/ecarrion.rss"/>
    <lastBuildDate>2016-06-09 10:13:18 -0400</lastBuildDate>
    <item>
      <title>A Story about Coordinators</title>
      <description>One approach to reduce the amount of code in ViewControllers is the Coordinator. But what is a Coordinator and how should we use it? Amongst other things, we'll talk about how Coordinators help make ViewControllers more re-usable by separating out the flow of the application, and how it improves the testability of the app. We'll also talk about how we introduced Coordinators bit by bit into an existing application, challenges we ran into, and the benefits we've found.</description>
      <media:content url="https://files.speakerdeck.com/presentations/e5407b474feb456cbbab882aece7c84b/preview_slide_0.jpg?6423166" type="image/jpeg" medium="image"/>
      <content:encoded>One approach to reduce the amount of code in ViewControllers is the Coordinator. But what is a Coordinator and how should we use it? Amongst other things, we'll talk about how Coordinators help make ViewControllers more re-usable by separating out the flow of the application, and how it improves the testability of the app. We'll also talk about how we introduced Coordinators bit by bit into an existing application, challenges we ran into, and the benefits we've found.</content:encoded>
      <pubDate>Wed, 08 Jun 2016 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/ecarrion/a-story-about-coordinators</link>
      <guid>https://speakerdeck.com/ecarrion/a-story-about-coordinators</guid>
    </item>
  </channel>
</rss>
