I work for a guy now who basically picked up some coding in his 30s because he found the previous business team he was on was more successful because of it.
His code isn't great, but he can express what he wants in giant SQL blobs and then we can build scalable solutions against basically his mockups. He can also unblock himself for a while with his own code while we build the real production flavor, etc.
It's great because he is basically expressing his requirements in something that works.
I think just like the coders should learn the business they work in, if the business learns some code.. everyone can be a lot happier.
In the low code context I think if you can all agree to treat whatever is generated there as throwaway prototypes, then it can be a value add. Ie - instead of writing a 20 page document, I'm going to show you something that sort of works here.
The pain comes from people thinking its going to replace developers, getting stuck, and then forcing the developers into the low-code tool too.
It's great because he is basically expressing his requirements in something that works.
I think just like the coders should learn the business they work in, if the business learns some code.. everyone can be a lot happier.
In the low code context I think if you can all agree to treat whatever is generated there as throwaway prototypes, then it can be a value add. Ie - instead of writing a 20 page document, I'm going to show you something that sort of works here.
The pain comes from people thinking its going to replace developers, getting stuck, and then forcing the developers into the low-code tool too.