&gt; just shifts how I encode the solution<p>And this is actually <i>the most important thing in industry software development.</i><p>It affects:<p>1. how easy it is to modify an existing codebase: eg., can you add feature X before your competitor even after you app grew to 1M LOC?<p>2. how easy it is for a new developer to start working productively on you codebase<p>3. how stable your software is: do modifications introduce subtle bugs that make the whole thing more and more unstable until it becomes unusable?<p>4. how secure your software is: how easy (read &quot;cost effective&quot;) is it to write secure code without having to take 10x longer to do this?<p>From a business perspective, the &quot;fundamental bottleneck is always what&#x27;s in your head&quot; problem can always be solved by temporarily hiring a few super-smart consultants with &quot;bigger heads&quot; that can get over this bottleneck, the rare times when you have the problem...<p>The rest of the time, the &quot;shape of your code&quot; is 100x times more important than the abstract formulation of an elegant solution. Because what you do 99% of the time is &quot;re-shaping&quot; existing code to do slightly different versions of what it already does, not solving interesting problems...<p>So yeah, at this level, <i>languages can make all the difference!</i>