What do you really get from IDE-driven development?
&gt; <i>How much effort, in the non-mathematical sense, are you willing to expend to discover if there is a lower minimum? Go over the hill to your left and you discover a minimum that is greater than the one you were just in. Go over the hill to the right and you find a lower minimum.</i><p>&gt; <i>This happens in just about anything you can imagine, but let’s consider IDEs. You start using an IDE and it makes one particular thing particularly easy, and it makes it so easy that you don’t go looking for something even easier. You can’t spend all of your time wondering if there’s a slightly better way of doing things.</i><p>This argument resonates fairly well with me. I generally view IDEs as low commitment, a rapid learning curve to completion, with very hard caps on what you are going to find. You&#x27;ll understand what the tool gives you, and then you&#x27;ll be done. There&#x27;s some trading&#x2F;collecting hooks to keep you feeling like you can improve, to collect all the best plugins to improve the base system, but you&#x27;re still a consumer, hunting for solutions, and you never really gain intimacy, understanding, or general prowess, evaluating your gains from a position of general ignorance as to what you&#x27;re really buying&#x2F;using. Being an end-user is being stuck at some minimum, having milked the curve you&#x27;re at, until someone else comes disrupts your world for you. You make no real gains on your own, develop no only superficial mastery, mastering of the pane-of-glass atop the environment you dwell in.<p>It&#x27;s really really hard to make a stronger better pitch for the school of lifelong learning &amp; struggle. Often IDEs are a great way to understand what is possible, what tools to expect, but once you have a baseline, getting back into the command line, the terminal, the console &amp; re-learning the hard way how to re-enact many of the things your IDE does for you is really hard. The learning curve is super slow, it takes ages to get out of the bottom reaches &amp; start to feel ok. But you&#x27;re gaining mastery not just of the programming job, but of the operating system, of the shell, of the real genuine honest environment of computing. Your ability to understand &amp; see what is happening is so much higher, has such a more real connection than the pane-of-glass interface. Your ability to evaluate &amp; direct yourself grows &amp; amplifies over time, only if you invest in yourself &amp; think of yourself as someone seeking a truthful engagement.<p>In general, I feel like the world has a lot of &quot;what is the use case&quot;&#x2F;&quot;what is the business value&quot; thinking, and there&#x27;s kind of an aggressive anti-exploratory value system that hates geekiness, that hates learning, that despises the enrichment of humankind, that rejects possibility. To insist on fast immediate obvious worth is to miss the big picture, is toxic to healthy ecosystems &amp; diversity&#x27;s neandering, exploring many many many tentacles. I want to see a world culture that believes in honest, genuine interactions, not fancy indecypherable veneers of things. Papert&#x27;s Constructivism&#x2F;Constructionism is a spiritual boon, one essential to what humanity became, and we should cherish, protect, &amp; grow this light. <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Constructionism_(learning_theory)" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Constructionism_(learning_theo...</a>