Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Purple
Assigned To: Russell A Moore
Created By: Russell A Moore
Created Date/Time: 7/9/2020 11:11 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 6596
Template/Type: Brandon Time
Title/Caption: Meeting with Russell
Start Date/Time: 7/15/2020 3:00 pm
End Date/Time: 7/15/2020 5:15 pm
Main Status: Active

Sorry, no photos available for this element of time.


Uploaded Media/Content & Other Files (1)
Media Name   File Type Date Description
Random_tick_list_for_the_fracture_project.docx   Doc/Text 7/16/2020 More random thoughts on the fracture system and where we are headed.


Notes:

Zoom meeting with Russell. We were talking about the dual ship model (older adilas system and newer adilas system - where we are headed). We spent some time talking about plans, needs, and requirements. Part of our plan needs to go through each section of the application and decide what is needed. Good planning on these sections will be awesome and will hopefully help us take inventory of what we have and what we want to keep, get rid of, and even upgrade to new functionality.

We talked a lot about the progression and natural growth of systems and applications. We were drawing diagrams of a circle - core and then add-on or bolt-on additions. Pretty soon, as soon as you get out a ways, the circle or core model starts looking like a flower vs a circle or core. We talked about how, you have to let it grow naturally and then eventually you rewrite it and then start over on the same progression cycles. That seems to be how things develop.

Russell and I jumped into some code review on the new corp-wide settings and defaults. We merged in some files and pushed up the new files to all servers. The new section looked great and hopefully will be accepted - sometimes we have people who can handle change and complain if we change anything.

After that, we jumped on a different project and I got my first look at the new add/edit payee/user permissions and saved roles (preset permissions and saved settings).

We talked about smaller micro processes that could play both ways between old and new. Some of these things were full on structural changes. The more we can play at the source, the better. This discussion got into talks about stateless services, language independent decisions, and even potentially looking at other coding languages. Currently, we have been using Adobe ColdFusion and that has worked great. There are times and seasons but we are being encouraged to keep looking around.

As the discussion continued, we started talking about planning "what" we want vs "how" you want it. I think our end goal is what we want... and it may not mater as much on the how we get there. Some of this comes down to research, preference, and skills. Those are not the only things, but we need to keep this door open right now.

At the end of the day, I kept recording some new ideas on my random tick list for fracture stuff. See attached.