Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Brandon Moore
Created By: Cory Warden
Created Date/Time: 4/28/2021 11:18 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 7769
Template/Type: Brandon Time
Title/Caption: Alan , Steve, Brandon and Cory-debrief vendor-outline items
Start Date/Time: 5/5/2021 11:30 am
End Date/Time: 5/5/2021 12:30 pm
Main Status: Active

Sorry, no photos available for this element of time.


Notes:

Alan gave Cory and I an overview on what he is working on, as far as progress and projects. Alan is majorly doing a refactor job on how new corporations are created inside of the system. The new process copies dummy tables vs static create new database SQL statements. This makes sure that we get the latest versions and helps with updates and changes. Good changes both coming and being mixed in.

We then switched over to enterprise level objects for corporations and vendors. Alan is doing a great job and marrying some code together in different places. Session objects. Both Wayne and Alan are working on similar projects with object models. Wayne, Alan, and Eric have also been working together on some other high level aggregate projects. That is awesome and I'm excited to see what comes of some of that interaction.

There were tons of other topics. Here are some of my notes:

- Lessons learned

- Memory management

- Referencing different instances

- Sharing object between corps

- Trade-offs on speed and performance

- Enterprise level mapping

- Trade-offs on simple vs complex

- Independent modules

- Unit testing

- Alan sees two main pieces or components in the testing. They are: 1=confidence and 2=testing from the get go and then going through things again later (built-in history and conservation of efforts).

- Going back allows you to get rid of bloated code and removing the extra pieces without breaking things

- Choosing which direction to go and then building those pieces or things independently

- Prepping for more future automated testing

- Certain testing practices may be a personality level decision, level of comfort on writing tests, complexity of the projects, and overall cost/benefit ratio

- Alan would love to encourage us to do more testing, where possible

- More and more small independent pieces of the code - knit together to make the whole

- Mentoring and helping others, hands on training and learning, one-on-one options for watching and learning

Towards the end of the meeting, we switched gears and talked about budgets and Cory had some questions for Alan about the delivery pieces and sending delivery information over the API sockets or endpoints. We have another project that will need to tie into those existing pieces. Lastly, we talked about a few other smaller projects and where they were at. Good meeting with lots of good ideas and reminders.