[rchaud]

Thank you. HN is one of the few places where no-code is discussed at length, and it's frustrating how many programmers default to replying with "I would never use this in production."

You don't have to. The no-coder is building a prototype, safely sandboxed away from your precious CI/CD pipeline. The benefit of building a robust prototype is that the idea-haver person doesn't bother developers with unfinished requirements, and the developers don't have to write a damn thing until they look through the prototype and start mapping out some changes.

[jtwaleson]

No-code is going to be used in production for sure. It's not something only for sandboxing and prototypes.

[rchaud]

My point is that the conversation about such tools is derailed by HN programmers who automatically jump to the conclusion that these products are the wet dreams of non-technical CEOs, who will force their org to go no-code exclusively.

If no-code tools are used in production, that implies that it will have to pass QA and code review, just like anything else.

[jtwaleson]

Completely agree with the sentiment.

But the definitions for both "production" and "application" are not so black and white. Take a super simple no-code app like a Google form survey. Some people would argue that that is not an app, others would say it is. Is it production? If I send that around to my team of 10 people, there will be no code review or QA. If I send it to 200 customers, then of course I let someone else review it.