The narrative of no code is no new story, but what does it mean for the future of software development and those who work to build it?
The ability to code is fast becoming a hygiene factor of skills.
I have a particular gripe to make before I jump into this topic, a blog post from an old development colleague revelled in the idea that very soon we will no longer need the intermediaries between the classic “business vs technology” structures you see within many organisations today. In essence it wasn’t just a nod to the end of Product Managers but a nod towards the shifting sands in education that sees software development make its way swiftly towards the standard school curriculum, the ability to code will soon become a hygiene factor of skills.
It’s a gripe as I as a Product Manager, have prided myself on bridging the technology gap for the last 10 years for direct employers and clients alike. The sheer dynamics of facing off against dozens of stakeholders all vying for space in priority and you having the keys to manage, decipher and execute on this wealth of knowledge to me is simply one of the best roles out there. To hear i’m due to suffer the same fate as the T-Rex of tech as I bow out in a blaze of glory is tough to hear. The argument is that due to the skills gap being closed both via education and in the “low code” mini revolution no longer will there be a need to have the bridge gapped to “translate” business needs into technical tasks. Business folk can dive straight in.
But who in practice loses out? Is it really the Product Manager with their business engagement, industry knowledge and logical thinking or is it the highly skilled Developer writing the software but whom at least on the surface of it is most under threat from tools that will replace their process of bringing ideas to life. If we take these roles as their industry standard job descriptions, I would initially argue it is the latter that loses out.
Ironically it appears that the high quality technologists of this world have built something overtime that will render them obsolete.
Building software has always been about process, logic and systematic thinking to support the notion of problem solving. With the rise of no code applications this process remains to be true, there is still a problem to be solved and still a neat workflow to be established all of which need to consider, legal, regulatory, marketing, UX, finance and data implications just as before. I’ve built & launched products on bubble.io and Adalo in the last month with fairly minimal effort except the underlying knowledge of what makes a good product. The workflow nature of these products allow’s for a very easy spin up of core workflow and features. Ironically it appears that the high quality technologists of this world have built something overtime that (at least on the surface) will render them obsolete, but perhaps only within the low hanging fruit of the market where simplistic personal & commercial apps are still to be made.
The second argument is that in building these no code systems, Developers as a community have given themselves much more room in which to start doing what they do (and love) best, working on brand new shiny things. All of which is coming in the onslaught of Web3, meaning that this no code threat is no more than a simple movement of the goal posts. After all, apps & websites are so 2008 and Web2, if the business & their product teams want a plug and play solution then let them have it. Developers will always have an opportunity to establish themselves in a brave new DAO entrenched world.
In short no-one becomes extinct, businesses arguably get more direct access, speed, control and a reduction in price, as they no longer rely on a human, but the Development world cycle as a whole should move on to bigger and better things. And guess what, it won’t be long before much larger & complex businesses are established and the need for the business vs gap bridgers vs technology will be required once again.
The Business vs Technology debate as a relationship has long been challenged in companies that resist the identification of an us vs them culture.
The fact is right now, that if you pick any current no code solution you still are constrained to an extent by the evolution of the software providers, are there enough integrations available? are the features rich enough to generate an experience that is truly unique and can flourish in a competition dense community? Whilst I believe that this is not too far from reality, today it is not the case. Not only would these systems have to become more robust but our standards would have to adjust, and perhaps not for the better. The Business vs Technology debate as a relationship has long been challenged in companies that resist the identification of an us vs them culture. Themes have been raised to combat this by creating more immersive and cohesive culture, where although we do not know where the Business ends and Technology starts, the inclusion of great minds will think alike. Companies cannot survive like this. It is this healthy conflict between the two parties that has seen so many of the best tech organisations flourish in the last 20 years, neither sides ever win out. But the healthy competition to strive for ground means that there are challenges amongst the ranks which make for greater ownership, accountability and better outcomes.
No-code could be worse than the cohesive world, it could mean the removal of one side of the balance all together. This isn’t just a threat to Developers but to the ecosystem of what governs a great product. Handing the master key to the business is not good for anyone, especially us consumers.
