JavaScript Fatigue: Realities of our industry (2017)
&gt; Technology is not a goal. Nobody cares about which programming language you are using, nobody cares about which frameworks your team has chosen, nobody cares about how elegant your data structures are and nobody cares about how good is your code.<p>100% that!<p>&gt; JS Fatigue happens when people use tools they don&#x27;t need to solve problems they don&#x27;t have.<p>Many JavaScript developers are scared (by scared I am paralyzed in the face of death catatonic scared to the most possible irrational extreme) to write original code when often times original code takes less time and is a better fit to the immediate problem.  This is called <i>Invented Here Syndrome</i> and is internally coddled when developers are appeased by writing configurations opposed to logic.<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Invented_here" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Invented_here</a><p>It is so bad that at my current employer somebody recommended I use a different editor to write code, because it had this kiss ass extension called Atom Beautify.  They were pretty forceful in their recommendation.  I am a collaborator on that project and wrote one of its beautifiers.  People are scared to death to write software themselves or use any software from people they know, but so long as they don&#x27;t I wrote any of it its great (to them).<p>&gt; Even though the ECMA spec is becoming more and more solid these days, we still need Babel.<p>I have always believed this is one of those not real problems the paper talks about immediately prior.  Writing cross browser JS is like writing CSS.  Everybody bitches about it but once you&#x27;ve nailed it you got it with ease forever.<p>&gt; My first advice for anyone suffering from JS Fatigue...<p>Learn the standards.  Code to the standards first.  Then optimize your workflow to become more efficient.  This is the very essence solving for <i>premature optimization</i>.