There's something like an 'uncanny valley' between RAD tools and a more 'best practices' setup/workflow. The upsides are obvious – someone that's not a 'softwa

There's something like an 'uncanny valley' between RAD tools and a more 'best practices' setup/workflow. The upsides are obvious – someone that's not a 'software engineer' can program things that do real work! The downsides tho are much less obvious; more 'hidden' costs really. It's easy and quick to bang out a new feature, but also really easy to inadvertently update or rollback another unrelated set of changes. As a professional programmer, I sure don't want to give up version control, unit tests, integration tests, automated builds, and automated deployments. Tho in fairness to RAD tools, and both the code they produce and the whole workflow involved in using them, when I started my current position the non-RAD-tool code was (much) worse, and much more difficult to refactor and cleanup, than the RAD-tool code.