<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Wittgenstein on Hillel Wayne</title>
    <link>https://www.hillelwayne.com/tags/wittgenstein/</link>
    <description>Recent content in Wittgenstein on Hillel Wayne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 10 Dec 2017 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.hillelwayne.com/tags/wittgenstein/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>What&#39;s the Right Tool for the Job?</title>
      <link>https://www.hillelwayne.com/post/right-tool/</link>
      <pubDate>Sun, 10 Dec 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.hillelwayne.com/post/right-tool/</guid>
      <description>&amp;ldquo;Use the right tool for the job&amp;rdquo; is a pretty tired cliche. Mostly it&amp;rsquo;s used to dismiss overengineering and one-size-fits-all solutions to problems, like using microservices for your 10-user app. It isn&amp;rsquo;t a bad saying, it&amp;rsquo;s just tautologically true. I don&amp;rsquo;t think anybody wants to use the wrong tool for the job, unless they&amp;rsquo;re trying to sabotage it. &amp;ldquo;Should I use the right tool for the job?&amp;rdquo; is a rhetorical question.</description>
    </item>
    
  </channel>
</rss>