Infrastructure Mistakes Companies Should Avoid
&gt; If you discovered the tool on Hacker News and it&#x27;s less than 18 months old — &#x27;Danger, Will Robinson!&#x27;<p>You shouldn&#x27;t fear new things.  Keep it simple, keep it smart, and embrace what works for your team.  Don&#x27;t shun things because they&#x27;re old, don&#x27;t shun things because they&#x27;re new.  Shun complexity.<p>How about a real-world examples?  Slack, Google Docs, and ZenHub.  All of these added value right out the gate.<p>I first read about Slack in February 2014 on Hacker News.<p>* We Don’t Sell Saddles Here – Medium || <a href="https:&#x2F;&#x2F;medium.com&#x2F;@stewart&#x2F;we-dont-sell-saddles-here-4c59524d650d#.b9koamhnq" rel="nofollow">https:&#x2F;&#x2F;medium.com&#x2F;@stewart&#x2F;we-dont-sell-saddles-here-4c5952...</a><p>Started playing with it, then started using it.  It&#x27;s helped my team move much faster.  Slack added value.  No reason not to use it.  Same for ZenHub, same for Zapier, same for Docker, same for a bunch of other tools where I can say, first-hand, that being an early-adopter paid off vs. using something &quot;tried and true.&quot;<p>Oh, and on that note, I freakin love Marker! (=<p>* Marker - Annotated Screenshots Sent to any Bug Tracking Tool || <a href="https:&#x2F;&#x2F;getmarker.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;getmarker.io&#x2F;</a>