3 ms·
I often try to do the same thing. But usually end up regretting it. From these experiences, both the successful and the failed ones, come a few gripes against
by ElFitz 4y ago
I often try to do the same thing.
But usually end up regretting it.
From these experiences, both the successful and the failed ones, come a few gripes against most low-code / no-code tools.
To name a few:
- Often poor, or completely absent, testability
- Often poor, or completely absent, versioning
- Conflating “saving” and “deploying to production”
- Lack of environments
- Often sorely lacking, sometimes poor, debugging tools and visibility
- Ridiculous choices (looking at you, Zapier and your absurd handling of JSONs and arrays of objects)
- Poor reusability
- Poor collaborative features
It is my understanding that for some products some improvements have been made on some the aspects I’ve mentioned.
But it also feels as if those behind these tools have completely ignored the progress we’ve made in software engineering best practices over the past 20 years.
- roflyear 4y agoOften just getting it kind of working is good enough. I don't like these solutions as they don't really give me full ownership of the problem space but I understand why people use them