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

Sorry, no photos available for this element of time.


Notes:

Alan, Steve, Dustin and I were on the morning meeting. The first little bit was each person reporting on what they were working on and what issues are still outstanding. Steve had a couple of questions for Alan and Dustin. They are following up on different tasks. I spoke with Alan a little bit about our plans for some changes in how the sub inventory and sub barcodes were going to be searched and filtered.

Next, I gave Steve a small update on my meeting with Spencer and Wayne from last week. He asked for some drawings on what was going on. I explained that Spencer was at a turning point where he was going to be needing access to actual data. He doesn't know Adobe ColdFusion very well yet, but he is a PHP master. PHP is another open source server side scripting language. Wayne and I decided that we would let Spencer build out his new prototype in PHP and use the adilas API sockets to get and pass data back and forth. That sort of spun us off into a small discussion on where are we going and how are we planning on integrating all of these pieces. That, of course, is a whole other topic. We touched on the need to build out the adilas API sockets (play at the wall - allow outside data connections) and how that would fit.

Calvin jumped on and a couple of the other guys bailed out. Steve and I had a good talk with Calvin. Our current project with Calvin is an outside label builder for custom and bulk labels. Part of our conversation was helping both adilas and Calvin get our communications being built up and on better levels. We chatted, got on the same page, and will hopefully be back on task next week. Calvin still has some other projects that he is working on right now. Good meeting.

Steve and I then spent some time talking about how the trend is kind of going toward 3rd party solutions and 3rd party build outs and then trying to inter connect them with internal adilas flow and processes. This took us back to a subject of PHP and other adilas API socket connections.

Eric popped in and had a couple of questions. He is building an project for sub special account tracking stuff like loyalty points, gift cards, etc. Some of our discussions today were dealing with page flow and naming conventions. We talked about having a new sub homepage for the special account tracking stuff. We then talked about how the user would have to let us know what special account type they were looking for information on, and then what that process would be like as they walked from step to step, adding filtering, and then finally results with drill-downs. Lots of concept level talks about flow and data. Good stuff and I think that Eric is making some good progress. We'll still need to tweak and refine things, but progress is being made.

Lots of emails and other things, just trying to get caught up and going. After that, Steve and I jumped back on the discussion about PHP, adilas API sockets, playing at the wall, internal vs public files, what servers would look like (just Adobe ColdFusion boxes, just PHP boxes, or dual setup of both ColdFusion and PHP per box). We have some questions that we will be asking Wayne about options and direction. We also made some good break trough's by noting which files and servers were private (owned and controlled by adilas) and which files and servers were public (owned by 3rd party and/or outside entities). Just adding what was public and what was private, really helped the conversation and get both Steve and I on the same page.

What we are seeing is that we need to keep pushing for a full separation between the data (database, storage, and access to the data), the logic (functions, methods, API sockets, and flow), and the actual display (what things look like, where they focus, and what they do or don't do - visual interfaces). Those three things data, logic, and display are huge. The more we separate them, the more modular our application becomes.

We didn't spend a ton of time on this... but all of our discussions were somewhat pointing to the greater and greater need for the adilas market (adilas world) to play a part in the puzzle. Currently, we have a saying "Play at the wall" for the adilas API sockets that we expose to the outside public. That wall is basically the access point between the adilas database and logic and the outside world. We are almost seeing a 2nd wall (virtually speaking) starting to form up. That second wall or outer wall is the adilas marketplace and who has what, who offers what, how is it obtained, or who has made pieces that  virtually are able to be plugged in and/or integrate with adilas core functions and functionality? I'm betting that the open market will end up playing a bigger and bigger role as things progress. Our challenge is how to manage that as it grows. Good stuff.