After a year of using Node.js in production
Now all of a sudden, having types and some standards to gather around doesn&#x27;t sound like a bad idea anymore ;)<p>I agree with one of the commenters: Lessons already learned by older engineers (who went through similar woes with other languages&#x2F;tools) are being re-learned again and again.<p>The software industry is in a sorry state.<p>Unless you are a very disciplined team with a very strong sense of writing modular code, don&#x27;t use Node.js for any larger project. 
And even then, the single-most useful function in an IDE &#x27;Show Call Hierarchy&#x27; will never be available when using a dynamically typed language.<p>That is not an issue for smaller projects. However, long before you even get close to the the million lines of code project size, your tools will fail you.
Your debugging&#x2F;refactoring times will explode and adding a new feature will seem unsurmountable.<p>Instead, let&#x27;s just re-write everything from scratch because the cool hipster that wrote your backend a year ago has left for greener pastures...<p>I won&#x27;t even try to guess the amount of technical debt produced with Node.js and the likes each day in the bay area.<p>And, yes, I just used Node.js to write a Slack-bot. It was fun, took me two hours and got me up and running quickly.
That&#x27;s the beauty of it. Just be aware of the dangers.