Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Brandon Moore
Created By: Brandon Moore
Created Date/Time: 9/20/2018 12:28 pm
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 4024
Template/Type: Brandon Time
Title/Caption: Adilas Time
Start Date/Time: 9/26/2018 9:00 am
End Date/Time: 9/26/2018 12:00 pm
Main Status: Active

Sorry, no photos available for this element of time.


Notes:

On the morning meeting with the guys. Steve, Josh, and Dustin were tracking down some of the new Metrc API stuff (killing plants and disposing of product). Alan came on and gave us a demo of what he is working on for the new invoice homepage. It will have some graphics, charts, and limited data being returned. Mostly some sums, historical data, and say the last 10 to 25 real transactions (for example, the last 10 invoices, the last 10 PO's, the last 10 expense/receipts, etc.). Great demo.

I was working on a runner upload for the Bear 100 mile runners. They will be using adilas this weekend to track their 100 mile race. Alan went back to working on his charts and graphs and Steve, Dustin, and Josh were working on syncing data between different systems.

We ended up having a really good conversation about dates, times, spans, buffers, logic stacking, data threads, and helping to do clean-ups. A lot of the conversation was dealing with how to sync up multiple servers (even potentially servers owned by different companies and/or systems) and how dates and times are pulled. Very interesting how things come back to time and how you sometimes have to either buffer and/or take spans into account. Time feels very solid and static, the problem becomes just like a line in the sand... if the record is on one side or the other, no problem. The problem comes in when it spans and/or plays through a given area (like a line in the sand). That gets tricky and the computer code or query has to be either flexible or somehow incorporate the span and/or buffer. Interesting how it kinda gets into adding in flexibility into a rigid or super tight system.

It reminds me of how we have seen this over and over again, how the system needs to flex and allow for bubbles and/or areas (virtual pods) where things can flex and then it comes back together at a future point and/or checkpoint. Here is an older entry with tons of good info (10/14/2014).

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=371&id=2894