fix broken links

Author: nathansgreen

archive.html

@@ -60,8 +60,6 @@ <h1>Blog Archive</h1>
 			<h4>May 2017</h4>
 			<ul>
 
-		<li>11 - <a href="blog/2013/unit-tests-as-experiments.html">Unit Tests as Experiments</a></li>
-		
 		<li>11 - <a href="blog/2017/unit-tests-as-experiments.html">Unit Tests as Experiments</a></li>
 	</ul>
 

feed.xml

@@ -9,18 +9,6 @@
     <pubDate>Wed, 10 May 2017 23:35:42 -0500</pubDate>
     <lastBuildDate>Wed, 10 May 2017 23:35:42 -0500</lastBuildDate>
 
-    <item>
-      <title>Unit Tests as Experiments</title>
-      <link>https://nathansgreen.github.io/blog/2013/unit-tests-as-experiments.html</link>
-      <pubDate>Thu, 11 May 2017 00:00:00 -0500</pubDate>
-      <guid isPermaLink="false">blog/2013/unit-tests-as-experiments.html</guid>
-      	<description>
-	&lt;p&gt;One of the strategies I&amp;rsquo;ve been using lately is creating unit tests when I have a problem that I don&amp;rsquo;t understand fully. It&amp;rsquo;s an easy way to encode a set of assumptions (test fixture setup), try out potential ways of solving a problem, then check whether it worked (assert some expected outcome).&lt;/p&gt;
-&lt;p&gt;Since I often work without a REPL (Java 9 will change this), I need easy ways to run programs that are small and malleable. I also work with complex runtimes (magical, auto-configured Spring systems are one of many examples) and it helps to be able to simulate a complex system by setting up test fixtures that manage that complexity while providing direct access to the thing I need to test.&lt;/p&gt;
-&lt;p&gt;I find this approach is also helpful when trying to work with an unfamiliar API. Sometimes my mental model of an API&amp;rsquo;s behavior doesn&amp;rsquo;t quite match reality, and a test is usually a quick way to verify an hypothesis about what outcomes I should expect.&lt;/p&gt;
-&lt;p&gt;The BDD way of structuring tests fits this approach pretty well. Given some initial conditions, when this thing occurs, then I expect this outcome. The difference is that instead of encoding requirements, I&amp;rsquo;m encoding hypotheses.&lt;/p&gt;
-	</description>
-    </item>
     <item>
       <title>Unit Tests as Experiments</title>
       <link>https://nathansgreen.github.io/blog/2017/unit-tests-as-experiments.html</link>

index.html

@@ -55,12 +55,6 @@
 	<div class="page-header">
 		<h1>Blog</h1>
 	</div>
-  			<a href="blog/2013/unit-tests-as-experiments.html"><h1>Unit Tests as Experiments</h1></a>
-  			<p>11 May 2017</p>
-  			<p><p>One of the strategies I&rsquo;ve been using lately is creating unit tests when I have a problem that I don&rsquo;t understand fully. It&rsquo;s an easy way to encode a set of assumptions (test fixture setup), try out potential ways of solving a problem, then check whether it worked (assert some expected outcome).</p>
-<p>Since I often work without a REPL (Java 9 will change this), I need easy ways to run programs that are small and malleable. I also work with complex runtimes (magical, auto-configured Spring systems are one of many examples) and it helps to be able to simulate a complex system by setting up test fixtures that manage that complexity while providing direct access to the thing I need to test.</p>
-<p>I find this approach is also helpful when trying to work with an unfamiliar API. Sometimes my mental model of an API&rsquo;s behavior doesn&rsquo;t quite match reality, and a test is usually a quick way to verify an hypothesis about what outcomes I should expect.</p>
-<p>The BDD way of structuring tests fits this approach pretty well. Given some initial conditions, when this thing occurs, then I expect this outcome. The difference is that instead of encoding requirements, I&rsquo;m encoding hypotheses.</p></p>
   			<a href="blog/2017/unit-tests-as-experiments.html"><h1>Unit Tests as Experiments</h1></a>
   			<p>11 May 2017</p>
   			<p><p>One of the strategies I&rsquo;ve been using lately is creating unit tests when I have a problem that I don&rsquo;t understand fully. It&rsquo;s an easy way to encode a set of assumptions (test fixture setup), try out potential ways of solving a problem, then check whether it worked (assert some expected outcome).</p>

sitemap.xml

@@ -1,9 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd">
-    <url>
-        <loc>https://nathansgreen.github.io/blog/2013/unit-tests-as-experiments.html</loc>
-        <lastmod>2017-05-11</lastmod>
-    </url>
     <url>
         <loc>https://nathansgreen.github.io/blog/2017/unit-tests-as-experiments.html</loc>
         <lastmod>2017-05-11</lastmod>