LowCode for the developer
That said citizen developers fail miserably in commonly adopted development best practices. Ever heard of spaghetti code? Train a citizen developer and give him unlimited access to your LowCode platform and you will soon find out that all benefits of LowCode will drop dead because they have no conceptual knowledge of redundancy, re-use architecture etc.
Does your platform not avoid this spaghetti code? Some do this better than others, however, it always requires a sturdy regime and discipline to keep architecture in check. and that is where most companies fail for a good reason. They were told with LowCode everything is faster, and so it is, you can create spaghetti code 10 times faster compared to traditional coding.
Regime and discipline can also be embedded in the platform like in no-code platforms, this is good for citizen developers but it does come with capability limits and leaky abstractions.
Traditional developers are often very skeptical at first, once they do see the benefits of the LowCode platform they tend to find their way around the challenges of the platform easily because they can always turn to traditional coding if the platform let's them. And yes, some platforms do that better than others.