3 ms·
The corollary of this is that low-code is best when a reusable component for a well-defined problem space exists. As soon as you drop into customized complexit
by ethbr1 3y ago
The corollary of this is that low-code is best when a reusable component for a well-defined problem space exists.
As soon as you drop into customized complexity, you should be building new low-code components with actual code.
Which I think is the main reason low-code is popular in the API-to-API SaaS space: actions are limited and well-defined.
- hinkley 3y agoNone of these solutions are low code though. Low code is using post-it notes to run your project. What "low-code" means is "someone else's code" and we already have tons of that, in the form of open source libraries and frameworks that avoid implementing tons of logic that is more or less idiomatic. This also includes SaaS solutions, where I am not running any code at all. You are, and I'm paying your for it. All I get are a palette of decisions I can make to alter how the product runs. Just like a YAML based solution. It's more snake oil, of an exact vintage that we already had in the late 1980's. And if you don't know what we called it then, it's because it was such a titanic flop that only computer history buffs know. An evolutionary dead end.
- ethbr1 3y ago> All I get are a palette of decisions I can make to alter how the product runs. It's amazing how many scenarios this covers. In the exact same way that IaaS abstracts away things a lot of people don't need to care about.
- hinkley 3y agoIt’s amazing how long you can unproductively stare at a piece of config that results in nothing happening when something was supposed to happen. Declarative code can be hell on beginners. It depends so much more than imperative or functional code on how clear the documentation is. And that was never our strong suit.
- ethbr1 3y agoI'd invert that and say "If you can't write clear documentation, quickly, on a low-code component, then it shouldn't be a low-code component." There are many things that low-code should never be used for. But there are a lot of things it can be. E.g. IFTTT type stuff
- michaelteter 3y ago> It's more snake oil Being able to model a system graphically and run that graphical model is invaluable when working with non-programmer domain experts. And as often happens when drawing pictures of things, we may see new ways to organize processes that are big improvements over the formerly-obvious way they were built. Another great use is allowing low-tech users to build their own low-code models. With a small bit of education, they can solve their own problems. And as some problems are short term situations, that low-code solution may suffice until the problem no longer exists. If the problem needs a long term professional solution, the developer can take the working low-code model and reimpliment it in code.
- hinkley 3y ago“Low code modules” is why everyone thinks Jira is hot garbage. It gets set up by a manager who makes a bunch of choices that sound good but are wrong. There was just a post on Reddit the other day claiming that if a developer sets up Jira, it’s a nice tool. It even has pretty pictures you can use for lifecycle definitions. That doesn’t help. We have spent years considering the consequences of decisions that sound nice but aren’t. Even if we only write five lines of code, that’s what you’re paying for. “Low-code” is “without programmers” and good luck with that.
- ethbr1 3y agoI'd say everyone things Jira is hot garbage because Jira's UX philosophy is "add a feature somewhere, when there's a customer who needs it." That works when you're SAP. Probably not for anyone else.
- mongol 3y agoWas it called 4GL?
- hinkley 3y agoWe have a winner.