First off, disclaimer, co-founder of Lowdefy [0] and shameless plug. But feel ok since it is on topic. I 100% agree with you on this. We’ve built many back-off

First off, disclaimer, co-founder of Lowdefy [0] and shameless plug. But feel ok since it is on topic. I 100% agree with you on this. We’ve built many back-office tools for customers and the bulk of the engineering time goes into understanding the problem and tranlating that into data. Tools like Lowdefy make it a lot easier to put this translation into action, but the real work is done by a data literate employee. We believe that role will stay with it the IT / dev department, at least for any project / tool larger than a Airtable. It use to be all tools larger than a spreadsheet or access DB, but now that scale has increased slightly but not much. For this reason we are designing Lowdefy to be a dev first low-code platform. By writing apps in a DSL you get the following advantages: - No steep learning curve for new devs :: All devs are familiar with DSLs. - Apps follow a structured schema :: Easy to pick up where others left off. - Nothing is hidden in a GUI :: You can copy, paste, find, replace, review changes, duplicate repos, etc. - Create and manage apps with code :: Develop scripts, like a visual app builder. - DSL files work with all dev tools :: Devs want to use their favorite tools. [0] - https://github.com/lowdefy/lowdefy https://github.com/lowdefy/lowdefy ---- With all this said, you can optimize with tools as much as you like - most dev productivity is always lost in building the wrong things.