Code vs. No-code
I&#x27;m a tad unusual in this discussion, because I write add-on code for a no-code tool (that you&#x27;ve never heard of, or instantly dismissed if you have.)<p>The timings might surprise you though. The tool&#x2F;language originated in DOS in the 80&#x27;s and moved to Windows in 1994. It allows you to work at the code, and no-code levels (intermingled) and allows you to write your own code to extend the no-code layer.<p>Which is what I started doing in 1992 for myself (because I&#x27;m lazy), addons which it turns out others wanted as well, and so gradually that has become a big part of my day job.<p>I still write programs in it though, and it&#x27;s fantastically productive. Mostly I build web apps now, but there are some big desktop systems in play and the odd mobile app as well.<p>Trends come and go, and it&#x27;s interesting to see the current discussion (now calling it no-code - at least it has a new name) while we quietly stay under the radar.<p>For reference there are maybe 5000 people total using this tool, most are in one-man or very small companies. Most are punching far (far) above their actual programming chops. None have ever seen a VC $. ) Most make a living writing either custom software, or niche products (or not so niche). Some are the underpinnings of very large and successful businesses. Very, very, few evangelise the actual product.<p>Yes all the negatives are in play. It&#x27;s a commercial system with infrequent upgrades (budget about $200 per year for the base product, say $500  pa for addons), zero marketing, anyone you hire has never heard of it, it&#x27;s archaic in some places (pretty good in others), has an IDE that occasionally crashes, plays OK (but not terribly well) with version control and so on.<p>&quot;real&quot; programmers turn their nose up at it (since the days when real programmers used C), and if it was ever &quot;cool&quot;, well, decades have passed since then.<p>But here&#x27;s the interesting thing. It allows people to find their place on the programming spectrum. They code as much, or as little, as they care to. Coloring inside the lines you can still make fantastic stuff. I know of companies that make a good living selling a product, and the (sole developer) can literally barely write a single line of code. I know of others who have written all the code by hand, and used very little of the no-code layer. The world is a spectrum and each finds his own place.<p>To dismiss no-code out of hand is to not really understand it. Word is like no-code to writers. Some use just spell checking, some for formatting, but there are still writers writing long-hand on paper because &quot;that&#x27;s the pure way, and paper never crashes&quot;.<p>I&#x27;ve written code in assembler. And C. And more. And that&#x27;s all fun, but it turns out customers don&#x27;t care what you write in. They care about the solution you are selling. What keeps our company of 50 people going is a program written mostly by 2 people, with code stretching back to the mid 90&#x27;s,but which easily beats out compeditors for functionality and cost and ultimately means we are a player in our space.<p>Of course no-code won&#x27;t solve every programming problem (although dropping to the code layer you pretty much can) but in the real world 99% of actually used, useful programs, are boring re-hashes or CRUD, APIs, Web Services, UIs, and so on. That&#x27;s the stuff people pay for which keeps the lights on.<p>And yeah, it&#x27;s fun to optimise string manipulations using assembler, or python, but that stuff doesn&#x27;t pay the bills.<p>Ultimatly no-code (with code) is not a new idea, it&#x27;ll never be the sexy thing, but it is very productive in the right hands, and it&#x27;ll be around for ages. Alas it takes time and effort to become skilled and experienced though, just like everything else.