<?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>Christopher Styles</title>
    <description></description>
    <link>https://speakerdeck.com/christopherstyles</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/christopherstyles.rss"/>
    <lastBuildDate>2013-10-31 14:43:28 -0400</lastBuildDate>
    <item>
      <title>Code Metrics For Improving Design</title>
      <description>Using code metrics, we can find problems in our software that make it hard for our design to change. This presentation shows an example of using complexity metrics to find a trouble spot, and a few first steps in the refactoring process.</description>
      <media:content url="https://files.speakerdeck.com/presentations/275901a024850131e54a0e1ba5e1dc33/preview_slide_0.jpg?2210122" type="image/jpeg" medium="image"/>
      <content:encoded>Using code metrics, we can find problems in our software that make it hard for our design to change. This presentation shows an example of using complexity metrics to find a trouble spot, and a few first steps in the refactoring process.</content:encoded>
      <pubDate>Thu, 31 Oct 2013 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/christopherstyles/code-metrics-for-improving-design</link>
      <guid>https://speakerdeck.com/christopherstyles/code-metrics-for-improving-design</guid>
    </item>
  </channel>
</rss>
