<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Eiffel on Hillel Wayne</title>
    <link>https://www.hillelwayne.com/tags/eiffel/</link>
    <description>Recent content in Eiffel on Hillel Wayne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 27 Nov 2017 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.hillelwayne.com/tags/eiffel/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Introduction to Contract Programming</title>
      <link>https://www.hillelwayne.com/post/contracts/</link>
      <pubDate>Mon, 27 Nov 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.hillelwayne.com/post/contracts/</guid>
      <description>I&amp;rsquo;ve namedropped contracts enough here that I think it&amp;rsquo;s finally time to go talk about them. A lot of people conflate them with class interfaces / dynamic typing / &amp;ldquo;your unit tests are your contract&amp;rdquo;, which muddies the discussion and makes it hard to show their benefits. So I&amp;rsquo;d like to build up the idea of contracts from first principles. We&amp;rsquo;re going to work in Python, up until the point where things get crazy.</description>
    </item>
    
  </channel>
</rss>