Well said.  My take on it is this - saying &quot;everyone should learn to code&quot; is NOT the same thing as saying &quot;everyone should become a developer&quot;.  By analogy, imagine saying that &quot;everyone should read&#x2F;write English&quot; is the same as saying &quot;everyone should become a novelist&quot;.<p>It&#x27;s not that everyone should become a developer as their profession, it&#x27;s that everyone, in every profession, can benefit from a bit of coding knowledge - just like they can benefit from speaking English. (For the sake of argument, let&#x27;s pretend this discussion applies to the US where most people speak English.  I&#x27;m over-simplifying by ignoring specific neighborhoods that are dominated by Spanish speakers, Chinese speakers, etc.  Substitute $YOUR_LANGUAGE in the preceding commentary if you&#x27;d prefer).<p>Now obviously there&#x27;s a <i>little</i> bit of hyperbole there.  Maybe not <i>every</i> profession in the most absolute sense, can benefit from coding. Or maybe they can.  But I think it&#x27;s safe to assume that pretty much any &quot;knowledge worker&quot; or &quot;white collar&quot; role can.  I mean, if you have to make decisions that involve data, or if there are processes you can automate, then coding can help you optimize your job &#x2F; business &#x2F; company &#x2F; whatever.<p>And even going beyond the traditional &quot;white collar &#x2F; knowledge worker&quot; role for a minute...  there&#x27;s a LOT to be said for the kind of automation you can enable at a grassroots &#x2F; DIY level if you can do some basic wiring, and program an Arduino or a rPi.   Are there applications for this stuff that apply to plumbers, welders, farmers, auto mechanics, etc., etc?   Almost certainly.<p>So yeah, definitely learn to code, just don&#x27;t think that necessarily implies &quot;move to Silicon Valley and become a full-time software developer&quot;.