Ironically a large part of my current job is writing code that runs on/interacts with a no/low code platform.
I would advise developers worried about these kind of tools to focus on the skill that really differentiates a developer who is basically effective from one who isn't, which is data modeling.
These things shine a spotlight on your high level data skills because you can't just code around bad database design decisions early in the project.
When the data is exported, your low level attention to detail and consistency come into focus. Did you encode Yes/No questions consistently? Were there free text fields where there should have been predefined options?
These low code/no code options are just revealing that coding was never the hard part of making software.
Ironically a large part of my current job is writing code that runs on/interacts with a no/low code platform.
Could you please elaborate? What tools do you interact with? Is this mostly backend work, getting the data out of no code tools for further processing?
I work with QuickBase and a few others. Data cleaning/import/export like you said are a big part of it but the larger aspect is client side JavaScript and working with whatever embedded language the platform has.
The other part is building custom apps that run alongside the no-code app, often backed by the API. I've implemented some fun things like transactions that lock so you don't have simultaneous write problems and full text search.
If you are in that business, the distinguishing features that I would look for is being able to use the relational model, an API or way to run code, and regulatory compliance (HIPAA, FERPA, 21 CFR Part 11). Native transactions would be a miracle (for instance update a record and associated child records and roll back if validation fails).
I would advise developers worried about these kind of tools to focus on the skill that really differentiates a developer who is basically effective from one who isn't, which is data modeling.
These things shine a spotlight on your high level data skills because you can't just code around bad database design decisions early in the project.
When the data is exported, your low level attention to detail and consistency come into focus. Did you encode Yes/No questions consistently? Were there free text fields where there should have been predefined options?
These low code/no code options are just revealing that coding was never the hard part of making software.