4 ms·
Hard-coded business logic: yuck. IIRC there's proprietary software (SDKs / integrations) specifically for specifying, running, testing and enforcing business ru
by anon49124 8y ago
Hard-coded business logic: yuck. IIRC there's proprietary software (SDKs / integrations) specifically for specifying, running, testing and enforcing business rules efficiently so that applications just present an API or respond to events rather than having to know everything about the business, and so not having to change N apps when a business rule changes / track down weird bugs when a business rule changes because another system didn't get a change also.
- adrianN 8y agoSome people prefer to "hardcode" business logic in Java instead of hardcoding it in XML or whatever business logic specification language the proprietary tools use. At least you can hire Java programmers fairly cheaply.
- mrweasel 8y agoI would pick hardcoding for most projects. You often end up creating a new DSL for your business logic, but because most of us aren’t language designers our DSLs end up being worse than what ever language the project is written in. Almost every time you will fail to correctly anticipate the future needs and your DSL won’t be sufficient anyway.
- ro_sharp 8y agoThe code is only hard if you can't release it safely.
- wiz21c 8y agoThat quite deepnds on the business. Some of our data scenario are super complex (thousands of datapoints, where one influence the others depending on how they happen in time, depending on manual intervention, things that happen here and there). Because of that, the usual tools to write your business logic fall short on the testing part. They're good at writing/maintaining simple rules, versioning them, but when a time dimension is crucial, then well, it's not that good anymore.