Low-code platforms have drastically risen in popularity over the last few years, primarily due to the need for faster application and automation development and, in some areas, the shortage of skilled ‘code-first’ developers.
According to a study conducted by Gartner, “by 2024, three-quarters of large enterprises will be using at least four low-code development tools for both IT application development and citizen development initiatives” (Gartner, 2020). Another report by Grand View Research projected that the global low-code development platform market size will reach USD 106.8 billion by 2027, growing at a CAGR of 22.5% from 2020 to 2027 (Grand View Research, 2021).
Many organisations have adopted, or started to adopt, low-code strategies for reasons other than speed, however. Cost is an important factor. Whilst low-code professionals can command healthy salaries within the UK, the pay disparity between low-code and ‘code-first’ developers is still apparent although this gap is decreasing year-on-year. But take-home pay aside, the cost of low-code platforms for organisations, in the long run, is more likely to be less than the infrastructure needed to develop, deploy, and maintain legacy services where, frequently, advanced computer or data scientists are needed from day one; often requiring a CV full of experience and certifications, pushing the matter of salary back into Finance colleague’s brains.
Low-code services, such as the Microsoft Power Platform, have a much faster time-to-market with, in many cases, improved agility. ‘Agile’ working methods, especially for technological development, has been the buzz-term for quite a few years now (who remembers the ‘waterfall’ approach? Sigh…) but what does agility really mean in this context.
Based on the Agile Manifesto (which I didn’t realise existed until recently), Agile development aims to focus on delivering work in planning increments, typically in two or four week ‘sprints’. This approach can, when managed effectively, allow for rapid adjustments based on the business needs, as well as ongoing, regular feedback and retrospective reviews. Agile development also emphasizes teamwork and collaboration, with cross-functional teams working together to achieve a common goal.
But, Agile is not perfect (what is?). The nature of cross-functional teams working together, especially in large organisations, can be difficult to achieve when working on large, distributed teams or projects that involve multiple stakeholders with conflicting priorities. The iterative nature of Agile development can make it challenging to track progress and manage timelines, especially when multiple sprints are running concurrently. Another potential drawback of Agile development is that it can be difficult to maintain a focus on quality while working in a fast-paced, iterative environment. The emphasis on delivering working software/apps/automation flows quickly can sometimes lead to shortcuts or compromises in quality, which can have negative impacts on the final product. But, all is not lost. Don’t get me wrong, Agile has a lot going for it, and I am a big proponent of it’s benefits and flexibility. Let’s focus on the aspect of quality, for a moment, however.
Code-first approaches to software development are exactly that; often pure code, coupled together with maybe a UI or integrations with legacy services, to provide complex solutions to business challenges. Many tools exists for pro-coders to check, validate and sandbox their code which are often really effective, but, unless you really understand the code to the point where you could literally write it with your eyes closed, the speed element of Agile can lead to rushed development and deployment. I’m not saying that a low-code approach eliminates this urge for deliverables (I’m the first to admit that my first foray into Power Apps a few years ago was far from perfect), but by having some more of the ‘basics’ taken care of with pre-built connectors and templates (with out of the box security features enabled), the focus on getting it right, rather than just ‘delivering’, is strengthened.
A Forrester report found that “79% of organizations have adopted or plan to adopt low-code development platforms” (Forrester, 2021). It’s clear that organisations are realising the power of low-code and, as such, there could well be an impact on the code-first developer community. Some say that low-code platforms may lead to a decreased demand for skilled developers, with an increasing need for such people to ‘upskill’ in low/no-code tooling to remain competitive. But let’s not get carried away, there will always be the need for ‘coders’, and I take my hat off to anyone who can write a script from scratch which does something that either low-code cannot, or to achieve customisation or enhancement on-top of a low-code solution.
So what does the future look like?
This is a difficult one. With the rise of services such as ChatGPT coming into the frame over the last few months, there are ways for those wishing to dip their toes into professional coding languages to do so without knowing what AI-generated code actually does. This is dangerous. ChatGPT is a brilliant advancement in AI-powered technology, but no developer (low or pro) should have reliance on its ability to write a script for you. Actually, I take that back; use it. It’s a great learning tool!
Moreover, Microsoft recently announced greater use of the OpenAI initiatives such as ChatGPT within their own infrastructure, so it must be doing something a lot right. The latest announcement is, currently a preview feature, of Power Virtual Agents to take any weblink and use the information on the webpage in a chatbot. Pretty nifty. ChatGPT’s API is also great for embedding into Power Apps and Power Automate, either via an HTTP request or creating your own ChatGPT Custom Connector. But, these are proof of concepts. Just don’t go copy and pasting its response blindly into your script/app/expression, is what I mean. This is a recipe for disaster.
In my view, the rise in low-code development will continue and, in some areas, surpass the advancement of the adoption of code-first approaches, especially when it comes to front-end business applications and automation. Having said this, let’s consider what, for example, the Power Platform is built ‘on top of’, so to speak. Microsoft Azure. If you’ve ever accessed the Azure Portal, you will see the services on offer. I dare you to go through the list of Azure services and see which could be replicated in a low-code approach; a fair few, but many require professional coders and developers to understand, let alone configure or use. So whilst companies invest, quite rightly, in low-code tools, embrace your pro-coders with every fibre of your being. There will come a time, shortly or in the coming months and possibly years, when we want to ‘do something’ using low-code tools that just isn’t possible without calling in favours from our VS-Code-loving chums.
How long will it take for low-code services to take advantage of these opportunities? Who’s to say?
