3 ms·
The escape hatch is where most low code products fall down, I think. This is because of market fit as you correctly point out, but not only that. It's also bec
by hitchstory 3y ago
The escape hatch is where most low code products fall down, I think. This is because of market fit as you correctly point out, but not only that.
It's also because knowing where the escape hatch and how to use it requires greater than average development skill and finesse and it isn't at all obvious when this is required.
The people who use these platforms aren't usually able to tell what kind of problem requires a developer and what kind of problem requires them doing just a bit more research. They're usually vaguely aware that the limit is out there somewhere but in the specific instances when they hit it they often don't know it's happened.
I've also seen some low code platforms get a little excitable about the idea of nearly or even fully reinventing the turing complete programming language to introduce more flexibility to their platform and make that their escape hatch. This is when things go really downhill.
- checkyoursudo 3y agoThis reminds me of the deskilling problem, where operators whose tasks are automated away and end up being relegated to monitors and troubleshooters need to be even more knowledgeable and skilled to identify and resolve the ever-more obscure problems/edge cases that the automation cannot handle, but because the operators do not perform those tasks any longer, there is no reasonable way for them to maintain their advanced level of knowledge and skill. And the more automated the processed get, the greater the deskilling problem. https://en.wikipedia.org/wiki/Ironies_of_Automation https://en.wikipedia.org/wiki/Ironies_of_Automation