<story><title>You Can&apos;t Buy Integration</title><url>https://martinfowler.com/articles/cant-buy-integration.html</url></story><parent_chain><item><author>keyle</author><text>I got bounced off a front-end job once, for not being good enough at React.&lt;p&gt;Mind you I&amp;#x27;ve been building SPA&amp;#x27;s since they weren&amp;#x27;t &amp;quot;a thing&amp;quot; and today I mostly use Vue.&lt;p&gt;But for that role, they didn&amp;#x27;t like my lack of .env variables in the front-end (such as for things that end up in the HTML), after a 3 hours coding test, and a couple of minor React-y tid bits they couldn&amp;#x27;t even clarify. Basically, not &amp;quot;idiomatic&amp;quot;.&lt;p&gt;Meanwhile, none of them could tell me how React actually works, beyond throwing jargon vomit. They couldn&amp;#x27;t write a web application without React. The recruiter, which we had to go through, basically had no empathy and saw me as a failed resume. I felt pretty helpless, even though I&amp;#x27;ve said many times to both parties that I wasn&amp;#x27;t a &amp;quot;React developer&amp;quot;.&lt;p&gt;That is the sad state of affairs today; and I&amp;#x27;m finding it&amp;#x27;s not just in the front-end, where you could argue that you need sanity on this pile of rubbles. It&amp;#x27;s also in the backend, especially on the auto-magic &amp;quot;DevOps!&amp;quot;</text></item><item><author>jefflombardjr</author><text>Really great read. Long but worth it.&lt;p&gt;This is a good critique of low-code&amp;#x2F;no-code in general. The root problem I see of &amp;quot;Unfortunately, when we frame the problem space that way, we have allowed our tools to think for us.&amp;quot; is that in reality there are just not enough qualified software engineers out there.</text></item></parent_chain><comment><author>sdevonoes</author><text>&amp;gt; Meanwhile, none of them could tell me how React actually works, beyond throwing jargon vomit. They couldn&amp;#x27;t write a web application without React. The recruiter, which we had to go through, basically had no empathy and saw me as a failed resume. I felt pretty helpless, even though I&amp;#x27;ve said many times to both parties that I wasn&amp;#x27;t a &amp;quot;React developer&amp;quot;.&lt;p&gt;But they don&amp;#x27;t make money by knowing &amp;quot;how React works&amp;quot;. They make money by &amp;quot;writing good-enough React code that pushes features to production&amp;quot;. I think get you, and in some sense I feel identified with you, it&amp;#x27;s just that the industry has shifted from &amp;quot;let&amp;#x27;s care about our craft&amp;quot; to &amp;quot;let&amp;#x27;s write good-enough code to make more money&amp;quot;... makes me sad, but hey, it&amp;#x27;s business I suppose.&lt;p&gt;I couldn&amp;#x27;t care less that a candidate knows what &amp;quot;React hooks&amp;quot; are (that&amp;#x27;s probably gonna be outdated in 1 or 2 years). I care if they know how to write modular code. Management doesn&amp;#x27;t have the same opinion, though: employees usually work for 1 to 2 years at the same company... so knowing what &amp;quot;React hooks&amp;quot; are now, matters for them.</text></comment>
<story><title>You Can&apos;t Buy Integration</title><url>https://martinfowler.com/articles/cant-buy-integration.html</url></story><parent_chain><item><author>keyle</author><text>I got bounced off a front-end job once, for not being good enough at React.&lt;p&gt;Mind you I&amp;#x27;ve been building SPA&amp;#x27;s since they weren&amp;#x27;t &amp;quot;a thing&amp;quot; and today I mostly use Vue.&lt;p&gt;But for that role, they didn&amp;#x27;t like my lack of .env variables in the front-end (such as for things that end up in the HTML), after a 3 hours coding test, and a couple of minor React-y tid bits they couldn&amp;#x27;t even clarify. Basically, not &amp;quot;idiomatic&amp;quot;.&lt;p&gt;Meanwhile, none of them could tell me how React actually works, beyond throwing jargon vomit. They couldn&amp;#x27;t write a web application without React. The recruiter, which we had to go through, basically had no empathy and saw me as a failed resume. I felt pretty helpless, even though I&amp;#x27;ve said many times to both parties that I wasn&amp;#x27;t a &amp;quot;React developer&amp;quot;.&lt;p&gt;That is the sad state of affairs today; and I&amp;#x27;m finding it&amp;#x27;s not just in the front-end, where you could argue that you need sanity on this pile of rubbles. It&amp;#x27;s also in the backend, especially on the auto-magic &amp;quot;DevOps!&amp;quot;</text></item><item><author>jefflombardjr</author><text>Really great read. Long but worth it.&lt;p&gt;This is a good critique of low-code&amp;#x2F;no-code in general. The root problem I see of &amp;quot;Unfortunately, when we frame the problem space that way, we have allowed our tools to think for us.&amp;quot; is that in reality there are just not enough qualified software engineers out there.</text></item></parent_chain><comment><author>qxmat</author><text>I&amp;#x27;ve worked with people of varying skill-levels but personally gravitate towards those who can code idiomatically. For me it&amp;#x27;s important I write idiomatic code and follow the language&amp;#x2F;framework&amp;#x2F;api guidelines to the letter so I don&amp;#x27;t become a maintenance burden to my team.&lt;p&gt;In the fast-paced world of frontend dev, the last thing I want to do is revisit &amp;quot;complete&amp;quot; work, be it a lack of env parametrisation or something bigger. We make assumptions based on idiomatic implementation - failing to conform means work-items can slip (&amp;quot;This story will slip into the next sprint because the I had to convert the callback into an idiomatic action&amp;#x2F;reducer first&amp;quot;).</text></comment>