Meeting with Kelly and Cory and Shari O. over a Zoom meeting. The main goal of the meeting was to look at some bad data for a client on data 10. We can't make it happen again, it was data from well over 1.5 years ago, and everything since then has been good. I'm just being silly, but it was a bit of a beat-up drill and a brow lashing of sorts. The good thing is we found the issue (limited number of bad records). At least we have a starting point to work from. We do not have a plan yet but that will come.

I was pitching the idea of a known issues report. Instead of just showing data (normal reports), we could actually look for bad data or errors in our code or data mismatches. That would be a small level of AI (artificial intelligence) on the reporting side. Imagine a report that said... check this and that... these things are known to be off the rails. That would be super cool. Side note, we actually started a known issues report way back (3/11/09)... at least listing out known areas that might have trouble. We just haven't been able to get around to building out that report. The actual report is in our code at this location... (top_secret/secure/known_issues.cfm). It has a huge list of possible problem areas, date mismatches, flow problems (something happened out of order or out of normal flow), and id/relationship possible problems.

As soon as we get a chance, it would be super cool to help uncover these and other possible problems and issues. Kelly had the idea of working backwards to help find the errors and exceptions.

One big take away, and something that we want to keep in mind for fracture (adilas lite) are these key pillars... We track money, inventory, finances, and full histories (Kelly was saying that those pieces are huge keys to what makes adilas awesome).