3 ms·
Have you done a lot of low code work? I’ve found it just ends up with escape hatches everywhere because the low code platform can’t handle some edge cases or ge
by iimblack 3y ago
Have you done a lot of low code work? I’ve found it just ends up with escape hatches everywhere because the low code platform can’t handle some edge cases or gets too complex for the non engineers to reason with. Other issues are observably, logging, testing, debugging, etc are often impossible or very difficult. Could work for small shops but the enterprises it gets marketed to usually need the normal code.
- dventimi 3y agoI do almost all of my work in the database. I don't know if you want to call that "low code" or not. Evidently, it doesn't look like code to many other developers but then again it precedes current low-code platforms by about 40 years, so who knows?
- iimblack 3y agoI wouldn’t call that low code but yeah the definition is ambiguous. I’m mostly experienced with and referencing flowchart type tools.
- dventimi 3y agoI'll grant I'm pretty skeptical of those.
- rcbdev 3y agoIf you use a procedural programming language (PL/SQL, T-SQL, etc.) to model your domain, you're just old-school programming. If you're using a tool like Oracle APEX you're doing Low Code, bar the few escape hatches.
- dventimi 3y ago> If you use a procedural programming language Occasionally, I use a procedural programming language in the database. Usually, I don't.