Earlier quoted context omitted.
Makes sense, that's what I've seen other folks do. I'm curious if you've seen them ask for more features over time, more actions, ability to manage the rules they write - and whether the full blown version of what they need was easy to support?
There's definitely room for growth - when has the business never asked for more haha. It's Agile were I work, so... Generally we deliver the basic UI with functionality to change one field/setting. See how they like it while we start working on the other fields. Assume they want more than they initially ask for because they overlook the details, like audit history and reporting stuff for example. And we obviously bui…
Ask HN: How do I spend less time updating “business logic”?
11–15 of 15 posts
Re: Ask HN: How do I spend less time updating “business logic”?
#12Founder of Seliom here. We provide a low-code business workflow automation platform, in which non-technical folks can update business logic quite easily. Happy to give you a demo. Check out our solution at https://www.seliom.com
What are your most commonly supported use case examples?
Re: Ask HN: How do I spend less time updating “business logic”?
#13Have you explored business rules engines[0] and business rule management systems[1] such as Drools[2][3]? - [0]: https://en.wikipedia.org/wiki/Business_rules_engine - [1]: https://en.wikipedia.org/wiki/Business_rule_management_syste... - [2]: https://www.drools.org/ - [3]: https://en.wikipedia.org/wiki/Drools
Re: Ask HN: How do I spend less time updating “business logic”?
#14Earlier quoted context omitted.
There's definitely room for growth - when has the business never asked for more haha. It's Agile were I work, so... Generally we deliver the basic UI with functionality to change one field/setting. See how they like it while we start working on the other fields. Assume they want more than they initially ask for because they overlook the details, like audit history and reporting stuff for example. And we obviously bui…
Thanks for sharing your story. Oh man, that sucks! Yeah, it's funny there's things I don't want to build in the first place. And then the moment you build them, you are responsible for making sure they work for the rest of your tenure. Managing downstream dependencies is genuinely hard for so many systems, and is made worse by the lack of visibility and custom code-writing for internal tools.
Re: Ask HN: How do I spend less time updating “business logic”?
#15Have you explored business rules engines[0] and business rule management systems[1] such as Drools[2][3]? - [0]: https://en.wikipedia.org/wiki/Business_rules_engine - [1]: https://en.wikipedia.org/wiki/Business_rule_management_syste... - [2]: https://www.drools.org/ - [3]: https://en.wikipedia.org/wiki/Drools
We looked into these, but they honestly seemed like a pain to integrate + getting ops to learn a new DSL would need org changes I can't really influence. Have you used these? Would love to hear more! I'd much rather not build it myself haha