There&#x27;s a trap hidden there as well, one I realized only recently - you not just realize how little you know, you are also increasingly unable to discern the importance of it.<p>Say you want to make a homepage. You&#x27;ve learned of Node.js, you&#x27;ve discovered Chef and Ansible, you&#x27;ve heard of Docker and Redis, you&#x27;ve seen Heroku and DigitalOcean. Where should you put it? Which tool should you use for automation? Is Grunt enough, or do you need Gulp? Which Yeoman generator should you use? Is LESS better than Sass?<p>The answer it: <i>it doesn&#x27;t matter, ignore that stuff</i>. Grab a random hosting (or VPS, if you know your way around Linux), hand-write some HTML and CSS, sprinkle with JS and that&#x27;s it. You don&#x27;t need IT infrastructure management, you don&#x27;t need build tools, you don&#x27;t need <i>any</i> stack. Just make that homepage, maintain it for a while, and notice which parts are the most annoying. Then think about how you could make those pain points disappear. <i>Then</i> see if any of those cool tools can help. It&#x27;s much easier to understand them if you know what problem they&#x27;re actually solving.