last couple of tweaks

Author: hjwp

blog/2020-08-13-so-many-layers.html

@@ -58,7 +58,8 @@ <h1> So Many Layers! A Note of Caution.</h1>
 comes with costs.  But just on the offchance that anyone was still missing the
 message and thinking we were saying that <em>all</em> apps should be built like this,
 I thought I&rsquo;d write a small blog post just to reinforce the message about
-costs.</p>
+costs.  If you&rsquo;ve been feeling tempted to cargo-cult every single pattern into
+every single app from now on, this should put you off.</p>
 <p>Each time you add a layer, you buy yourself some decoupling, but it
 comes at the cost of an extra moving part.  In the simplest terms, there&rsquo;s an
 extra file you have to maintain.</p>
@@ -75,7 +76,7 @@ <h1> So Many Layers! A Note of Caution.</h1>
 through the stack, because things have to change all the way from the
 frontend/UI, all the way down to the database.</p>
 <p>If you&rsquo;re using a framework like Django, you might be used to thinking of a
-change like this, in a perfect world, as a change you can make to just <strong>one</strong> file.
+change like this, in a perfect world, as a change you can make to just <em>one</em> file.
 You would change <code>models.py</code>, and then your <code>ModelForm</code> will be updated automatically,
 and maybe even the frontend will &ldquo;just work&rdquo; too, if you&rsquo;re using the form&rsquo;s
 autogenerated HTML.  That&rsquo;s one of the reasons that Django is so good as a
@@ -136,7 +137,7 @@ <h1> So Many Layers! A Note of Caution.</h1>
 forms.  We want to make it easy to capture complex and evolving business
 requirements in a <a href="/book/chapter_01_domain_model.html">domain model</a>.  But, as we try to say in each chapter,
 your mileage may vary!</p>
-<div id="#in_theory"><small><i>
+<div id="in_theory"><small><i>
   OK, in theory.  In practice, I think this particular app was a _little_
   overengineered. It was one of the first ones that the team had complete
   freedom to try new patterns on, and they may have gone to town a bit...

posts/2020-08-13-so-many-layers.md

@@ -7,7 +7,8 @@ In the book we are at pains to point out that each pattern is a trade-off, and
 comes with costs.  But just on the offchance that anyone was still missing the
 message and thinking we were saying that _all_ apps should be built like this,
 I thought I'd write a small blog post just to reinforce the message about
-costs.
+costs.  If you've been feeling tempted to cargo-cult every single pattern into
+every single app from now on, this should put you off.
 
 Each time you add a layer, you buy yourself some decoupling, but it
 comes at the cost of an extra moving part.  In the simplest terms, there's an
@@ -29,7 +30,7 @@ through the stack, because things have to change all the way from the
 frontend/UI, all the way down to the database.
 
 If you're using a framework like Django, you might be used to thinking of a
-change like this, in a perfect world, as a change you can make to just **one** file.
+change like this, in a perfect world, as a change you can make to just _one_ file.
 You would change `models.py`, and then your `ModelForm` will be updated automatically,
 and maybe even the frontend will "just work" too, if you're using the form's
 autogenerated HTML.  That's one of the reasons that Django is so good as a
@@ -96,7 +97,7 @@ forms.  We want to make it easy to capture complex and evolving business
 requirements in a [domain model](/book/chapter_01_domain_model.html).  But, as we try to say in each chapter,
 your mileage may vary!
 
-<div id="#in_theory"><small><i>
+<div id="in_theory"><small><i>
   OK, in theory.  In practice, I think this particular app was a _little_
   overengineered. It was one of the first ones that the team had complete
   freedom to try new patterns on, and they may have gone to town a bit...

rss.xml

@@ -7,7 +7,7 @@
             Simple patterns for building complex apps
         </description>
         <link>https://www.cosmicpython.com</link>
-        <lastBuildDate>Mon, 17 Aug 2020 05:53:06 -0000</lastBuildDate>
+        <lastBuildDate>Mon, 17 Aug 2020 06:02:42 -0000</lastBuildDate>
         <pubDate>Sat, 4 Jan 2020 19:15:54 -0500</pubDate>
         <atom:link href="https://cosmicpython.com/rss.xml" rel="self" type="application/rss+xml" />