<?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>ExpensiveBelly</title>
    <description></description>
    <link>https://speakerdeck.com/expensivebelly</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/expensivebelly.rss"/>
    <lastBuildDate>2016-05-11 06:33:09 -0400</lastBuildDate>
    <item>
      <title>Working Effectively with Android Legacy Code</title>
      <description>Android developers face a tough challenge when working with legacy code including God activities, code coupling and issues integrating new features, to name just a few. What other blockers are there to working with legacy code and what are the solutions to such challenges?</description>
      <media:content url="https://files.speakerdeck.com/presentations/1c0394496e234a52905a0de50b0ed7ca/preview_slide_0.jpg?6345821" type="image/jpeg" medium="image"/>
      <content:encoded>Android developers face a tough challenge when working with legacy code including God activities, code coupling and issues integrating new features, to name just a few. What other blockers are there to working with legacy code and what are the solutions to such challenges?</content:encoded>
      <pubDate>Tue, 10 May 2016 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/expensivebelly/working-effectively-with-android-legacy-code</link>
      <guid>https://speakerdeck.com/expensivebelly/working-effectively-with-android-legacy-code</guid>
    </item>
  </channel>
</rss>
