3 lines of code shouldn't take all day
This is probably a controversial opinion, but I think that working in an environment where time-to-iterate is high is actually very beneficial for improving your skills. It&#x27;s one of those things that may feel overly burdensome in the short term, but is better in the long term. I say this as someone who taught programming with beginners, and observed what many of them will do when given an IDE, which at the scale of the code they&#x27;re writing, makes the time-to-iterate <i>very</i> short (press a key and you instantly see your changes). They end up getting into a &quot;dopamine feedback loop&quot; that causes them to continually make tiny changes and rebuild&#x2F;run, and the code written as a result of this looks exactly like what you&#x27;d expect: it barely works, and is full of redundancies, &quot;dead ends&quot;, and other evidence that its author was probably not thinking of anything more than the next line or two when writing it.<p>In other words, reducing the iteration time reduces the motivation to get it right the first time, and the associated deep reasoning&#x2F;&quot;mental execution&quot; skills which are required to do so. In order to develop those skills, one should strive to write as much code as possible before running it, and a high iteration time assists with that.<p>Also, I&#x27;m tempted to continue the title with &quot;...unless it&#x27;s APL&quot;.