diff --git a/client/src/blog/posts/4.js b/client/src/blog/posts/4.js
index 2d522c3..4e5672c 100644
--- a/client/src/blog/posts/4.js
+++ b/client/src/blog/posts/4.js
@@ -37,6 +37,8 @@ let body = <div>
   <p>Those are two extremes - target somewhere in between, see my <Link to="/1">list of job boards</Link>. Apply to medium-sized companies.</p>
 
   <h4>Conclusion</h4>
+  <p>Thing is, my wife <em>actually</em> started making cash before knowing the definition of "algorithm". Experience is people who disagree do so on principle, not evidence. Their example is some offshore-borked project (compared to American artisanal code) and their mustachios quiver with rage. If you disagree, ask yourself - are you a hipster? Maybe it's the "Uncertainty Principle" as my real-life examples I partially coach. Perhaps striking out on your own without a helping hand is a different story. But I keep hearing the same thing over: "you need the fundamentals," and I keep seeing that <em>actually</em> proven wrong. To me evidence speaks louder than theory.</p>
+
   <p>You don't have to be <em>the best</em> to succeed in this industry. Not everyone need be an engineer; some can be coders. You don't need countless years' experience in substack languages, understanding pointers and registers or a framework's history to succeed. Those nuggets will help you absolutely, but they're not strictly necessary. Am I encouraging mediocrity? Of course not, but the barrier to entry is lower than the nay-sayers say. You'll learn what you need as you go, and you have to start somewhere. <Link to="/2">Start here!</Link>.</p>
 
 </div>;