4 ms·
> 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
by 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.