<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>coding on James Alvarez</title><link>https://jamesalvarez.co.uk/tags/coding/</link><description>Recent content in coding on James Alvarez</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Tue, 28 Jun 2022 00:00:00 +0100</lastBuildDate><atom:link href="https://jamesalvarez.co.uk/tags/coding/index.xml" rel="self" type="application/rss+xml"/><item><title>Do I have Javascript fatigue?</title><link>https://jamesalvarez.co.uk/blog/javascriptfatigue/</link><pubDate>Tue, 28 Jun 2022 00:00:00 +0100</pubDate><guid>https://jamesalvarez.co.uk/blog/javascriptfatigue/</guid><description>&lt;p&gt;Recently I had to spend a few hours updating a React project, and fixing breaking changes from all the new dependencies and upgrades on npm packages, and in timely fashion I came across this article discussing &lt;a href="https://medium.com/@ericclemmons/javascript-fatigue-48d4011b6fc4"&gt;Javascript fatigue&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This point landed particularly hard, especially after spending more than an hour figuring out why my source maps were no longer working:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Ultimately, the problem is that by choosing React (and inherently JSX), you’ve unwittingly opted into a confusing nest of build tools, boilerplate, linters, &amp;amp; time-sinks to deal with before you ever get to create anything.&lt;/p&gt;</description></item></channel></rss>