<?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>Hugh Noble</title>
    <description/>
    <link>https://speakerdeck.com/hughnoble</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/hughnoble.rss"/>
    <lastBuildDate>2018-12-05 08:14:13 -0500</lastBuildDate>
    <item>
      <title>4 rules for happier objects</title>
      <description>Having a good code structure helps your software to be maintainable and flexible well into the future. As software developers it’s our job to ensure the software is maintainable and refactorable. 

The structure of code can make a big difference to how fragile and prone to bugs an application is. By embracing some simple guidelines and patterns we can write software that's more maintainable, flexible, less bug prone, and more fun to work with. </description>
      <media:content url="https://files.speakerdeck.com/presentations/0dd0ae788a4c4b60912ce8a1eed3b806/preview_slide_0.jpg?11370802" type="image/jpeg" medium="image"/>
      <content:encoded>Having a good code structure helps your software to be maintainable and flexible well into the future. As software developers it’s our job to ensure the software is maintainable and refactorable. 

The structure of code can make a big difference to how fragile and prone to bugs an application is. By embracing some simple guidelines and patterns we can write software that's more maintainable, flexible, less bug prone, and more fun to work with. </content:encoded>
      <pubDate>Wed, 21 Nov 2018 00:00:00 -0500</pubDate>
      <link>https://speakerdeck.com/hughnoble/4-rules-for-happier-objects</link>
      <guid>https://speakerdeck.com/hughnoble/4-rules-for-happier-objects</guid>
    </item>
  </channel>
</rss>
