all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
Blue
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Notes:
|
|
On a 1 hour GoToMeeting session with a developer from the Jane Team. We were making some changes to the API and then pushing things up for him to test. Our changes were pretty fast. However, his debugging and error log process was crazy. So much information it almost made it impossible to find anything. Once you found things, it was great because you have tons of info but to find it was a crazy process. As a side note, we watched him (the other developer) navigate a newer more modern database platform that stored data objects and JSON objects for every record. Very flexible but that type of a model wouldn't work with our business model. The data was all there, but it was stored as a huge glob of data and the user had to expand and contract the data to see what was there. The query and look-up options looked crazy as well. I'm very grateful that we are using a traditional database model with tables, fields, and normal SQL queries. We do use JSON object storage but only in certain places. It is great to store tons of stuff, but it totally dies if you need to run queries, filters, reports, or aggregate functions (max, sum, average, min, counts, etc). If you only need things one at a time, it rocks. If you need multiple things at once or need to access things over and over again in bulk, it struggles. Too much overhead. I think we'll stick to what we have. Bryan and I then worked on some code sign-off for his API changes. This project has opened up a lot of unknown holes but that is good. At the end of the day, we went over some of the logic on his new project for in-line discounts and doing dollars off discounts. Some of the files have a lot of javascript and that makes that project a little bit tougher. We'll get it done... |