I'm quite bullish about low-code tools now. Especially for building back office systems like ERPs or operational tools. From my experience most failures in such project implementations have been due to mismanagement in the requirement gathering phase and also development happening in silos where the team building has no real understanding of the business process workflows.
But with gpt-3.5 - these tools can really inlock the ability of non technical people to build products. Maybe outsystems should have a gpt chat interface that builds software on its platform directly from the requirements of the end user instead of any intermediate human development team.
Having used low-code tools successfully to build ERP systems for the past few years.
I feel low code tools can only really disrupt development once they solve the problem of requirements gathering from customers/ end users and also formally describe change management in low-code as well. As long as there is ambiguity in requirements - code or low code makes no difference.
This is a good point. Most comments about the rewrite in code being easier might actually be because the functional requirements from the business users have already been made clear without the ambiguity that might have arisen when developing from scratch.
I am assuming your models are not opensource/openweights?