{"id":736,"date":"2023-04-13T14:57:20","date_gmt":"2023-04-13T20:57:20","guid":{"rendered":"https:\/\/redmonk.com\/rstephens\/?p=736"},"modified":"2023-04-13T14:57:20","modified_gmt":"2023-04-13T20:57:20","slug":"llms-vs-low-code","status":"publish","type":"post","link":"https:\/\/redmonk.com\/rstephens\/2023\/04\/13\/llms-vs-low-code\/","title":{"rendered":"The Pending Collision of LLMs and No-Code\/Low-Code Platforms"},"content":{"rendered":"<p>We recently had a couple different clients bring up the concept of &#8220;prompt engineers,&#8221; speculating on a future where engineering would be less about the creation of the code itself and more about the process of creating and curating AI-generated prompts.<\/p>\n<p>The framing about what these prompt engineers might theoretically do felt remarkably similar to the stories and promises we\u2019ve heard about the no-code\/low-code space, which was interesting to me.<\/p>\n<p>I can&#8217;t count how many developers and engineers over the years I&#8217;ve chatted with who actively distrust the outputs of no-code platforms, despite claims that it will speed and &#8216;democratize&#8217; development. It&#8217;s notable that the idea of \u201cbuilding a website without ever needing to write source code\u201d has taken the world by storm when it&#8217;s being done with AI\/ML but is something we collectively tend to discount when it&#8217;s done with low-code.<\/p>\n<p>So what&#8217;s the difference, and what does the introduction of LLMs mean for low-code platforms?<\/p>\n<p>The primary justification for low-code platforms is allowing teams to move quickly from idea-to-deployment with no code input required.<\/p>\n<p>Given what we&#8217;ve witnessed in the last few months, it&#8217;s inarguable that AI-code generation is going to have some impact on this space. The purported and demonstrated abilities of AI to generate code (<a href=\"https:\/\/twitter.com\/thekitze\/status\/1635737773964492817\">in some cases from very abstract descriptions<\/a>), <a href=\"https:\/\/twitter.com\/rakyll\/status\/1535369047638183936\">create scaffolding<\/a>, <a href=\"https:\/\/twitter.com\/simonw\/status\/1645959248629886978\">help brainstorm, test and prototype<\/a>, and otherwise speed up the development process is well documented. See my colleague <a href=\"https:\/\/redmonk.com\/jgovernor\/2023\/04\/13\/the-great-flowering-why-openai-is-the-new-aws-and-the-new-kingmakers-still-matter\/\">James Governor&#8217;s post on AI&#8217;s impact on the &#8220;revolution of idea-to-code.&#8221;<\/a>.<\/p>\n<p>LLM vs. low-code is not an apples-to-apples comparison. The primary difference between LLMs and low-code platforms is the output. Generally, when you tell an LLM to generate a website, it spits out actual code in an actual language that will run anywhere. When you tell a low-code platform that, it either won\u2019t (black box) or it spits out incomprehensible and\/or proprietary code that, often enough, can only be run on a single proprietary platform.<\/p>\n<p>There are still plenty of use cases where low-code will still be the right choice. If you&#8217;re an organization that doesn\u2019t want anything to do with infrastructure and don\u2019t care about the underlying platform, then low-code might still be the best bet.<\/p>\n<p>If you care about portability at all LLMs will probably be an appealing alternative.<\/p>\n<p>LLMs won&#8217;t take the whole market, but it seems likely they&#8217;ll take some of the growth out of the market. Existing low-code customers and their apps are unlikely to migrate, but low-code platform growth is going to become more difficult to come by.  Low-code providers have reason to be concerned about their future growth prospects.<\/p>\n<p><a href=\"http:\/\/redmonk.com\/rstephens\/files\/2023\/04\/AdobeStock_158554458-scaled.jpeg\"><img decoding=\"async\" src=\"http:\/\/redmonk.com\/rstephens\/files\/2023\/04\/AdobeStock_158554458-scaled.jpeg\" alt=\"Silhouettes of workers building scaffolding at sunset\" width=100% class=\"aligncenter size-full wp-image-735\" srcset=\"https:\/\/redmonk.com\/rstephens\/files\/2023\/04\/AdobeStock_158554458-scaled.jpeg 2560w, https:\/\/redmonk.com\/rstephens\/files\/2023\/04\/AdobeStock_158554458-520x194.jpeg 520w, https:\/\/redmonk.com\/rstephens\/files\/2023\/04\/AdobeStock_158554458-1024x382.jpeg 1024w, https:\/\/redmonk.com\/rstephens\/files\/2023\/04\/AdobeStock_158554458-768x287.jpeg 768w, https:\/\/redmonk.com\/rstephens\/files\/2023\/04\/AdobeStock_158554458-1536x573.jpeg 1536w, https:\/\/redmonk.com\/rstephens\/files\/2023\/04\/AdobeStock_158554458-2048x764.jpeg 2048w, https:\/\/redmonk.com\/rstephens\/files\/2023\/04\/AdobeStock_158554458-480x179.jpeg 480w, https:\/\/redmonk.com\/rstephens\/files\/2023\/04\/AdobeStock_158554458-1200x448.jpeg 1200w\" sizes=\"(max-width: 2560px) 100vw, 2560px\" \/><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>We recently had a couple different clients bring up the concept of &#8220;prompt engineers,&#8221; speculating on a future where engineering would be less about the creation of the code itself and more about the process of creating and curating AI-generated prompts. The framing about what these prompt engineers might theoretically do felt remarkably similar to<\/p>\n","protected":false},"author":45,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","footnotes":"","jetpack_publicize_message":"The Pending Collision of LLMs and No-Code\/Low-Code Platforms","jetpack_is_tweetstorm":false},"categories":[40,126,127,125],"tags":[],"class_list":["post-736","post","type-post","status-publish","format-standard","hentry","category-ai","category-llms","category-low-code","category-platforms"],"jetpack_featured_media_url":"","jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/redmonk.com\/rstephens\/wp-json\/wp\/v2\/posts\/736","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/redmonk.com\/rstephens\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/redmonk.com\/rstephens\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/redmonk.com\/rstephens\/wp-json\/wp\/v2\/users\/45"}],"replies":[{"embeddable":true,"href":"https:\/\/redmonk.com\/rstephens\/wp-json\/wp\/v2\/comments?post=736"}],"version-history":[{"count":0,"href":"https:\/\/redmonk.com\/rstephens\/wp-json\/wp\/v2\/posts\/736\/revisions"}],"wp:attachment":[{"href":"https:\/\/redmonk.com\/rstephens\/wp-json\/wp\/v2\/media?parent=736"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/redmonk.com\/rstephens\/wp-json\/wp\/v2\/categories?post=736"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/redmonk.com\/rstephens\/wp-json\/wp\/v2\/tags?post=736"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}