2 ms·
People written SQL scripts that check for scenarios, and even potentially action / repair them is a form of intelligence. It's not artificial, either. Thinking
by j45 9y ago
People written SQL scripts that check for scenarios, and even potentially action / repair them is a form of intelligence. It's not artificial, either.
Thinking back to successful ERP implementations, little was more useful during go-live or an ongoing basis than a script that ran every hour/day/week/month to look for a condition and report it.
In one case, over a 3 year period where the organization grew from 0 to 60 million per year, every data issue was logged as a ticket, investigated, where needed, a Sql script written to monitor other occurrences, and ultimately, if there was a need to action, it would be forwarded to the right destination with a link to instructions on how to resolve or investigate if a decision could not be programmatically made.
The power of this was users received direct and immediate feedback anytime they wanted if their work was good and compliant with the system and process.
How did the list of scripts to build get made? Every time the system behaved correctly or incorrectly, and needed attention, whether due to data being incomplete, mis-entered, or correct and ready for the next step, the technology was busy working for the users.
Scripts reduced concerns that issues were being missed. Once something had happened and it was important enough, a custom insight could be built. It helped build a data driven culture instead of hoping the computer picked the right thing.
Sql scripts could one day feed into or fit with AI/ML. I don't see that day here in the short term.