<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: software-erosion</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/software-erosion.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2011-06-29T17:26:00+00:00</updated><author><name>Simon Willison</name></author><entry><title>The New Heroku (Part 4 of 4): Erosion-resistance &amp; Explicit Contracts</title><link href="https://simonwillison.net/2011/Jun/29/heroku/#atom-tag" rel="alternate"/><published>2011-06-29T17:26:00+00:00</published><updated>2011-06-29T17:26:00+00:00</updated><id>https://simonwillison.net/2011/Jun/29/heroku/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://blog.heroku.com/archives/2011/6/28/the_new_heroku_4_erosion_resistance_explicit_contracts/"&gt;The New Heroku (Part 4 of 4): Erosion-resistance &amp;amp; Explicit Contracts&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
I really like Adam’s description of Software Erosion—I’ve seen that happen to my projects a bunch of times, and it really is an important problem to solve.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/heroku"&gt;heroku&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/recovered"&gt;recovered&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/software-erosion"&gt;software-erosion&lt;/a&gt;&lt;/p&gt;



</summary><category term="heroku"/><category term="recovered"/><category term="software-erosion"/></entry></feed>