Ask HN: Problems worth solving with a low-code back end?
I have built a low-code (textual) backend builder that allows writing a backend as functions. For example, a (part) of a backend that calculates average of an integer array and then prints it out:
Now I am trying to find problems worth solving with it to verify builder's expressiveness and limitations. So far I haven't really encountered suitable problems. I have researched many lowcode/workflow automation tools/builder and their shared use-cases or success stories, but to me they just show-case how little they can achieve.
Have you used a low-code backend builder already for some ambitious/cool problems/use-cases? Or do you have a such problem/use-case in mind? If you would evaluate a low-code backend builder, how would you do it?
### average=AVERAGE([1,1,2,3,5,8]) ECHO(average) ###
Now I am trying to find problems worth solving with it to verify builder's expressiveness and limitations. So far I haven't really encountered suitable problems. I have researched many lowcode/workflow automation tools/builder and their shared use-cases or success stories, but to me they just show-case how little they can achieve.
Have you used a low-code backend builder already for some ambitious/cool problems/use-cases? Or do you have a such problem/use-case in mind? If you would evaluate a low-code backend builder, how would you do it?