Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Brandon Moore
Created By: Brandon Moore
Created Date/Time: 7/2/2018 11:10 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 3884
Template/Type: Brandon Time
Title/Caption: Adilas Time
Start Date/Time: 7/3/2018 9:00 am
End Date/Time: 7/3/2018 1:45 pm
Main Status: Active

Sorry, no photos available for this element of time.


Notes:

Dustin, Alan, Wayen, and I were on the morning meeting. Small demo by Wayne on object oriented coding. We were seeing all kinds of service objects, data objects, database access objects, and other models. This all goes back to the keeping the data, the validation, the business logic, and the database stuff all on different levels. That just makes the code more re-usable and more logical to follow (both internal and external). All of this makes things more modular and easy to use.

We spent a little bit of time talking about MVC's (model view controller). Each area is different. You have the model, the view, and the controller piece. They are all kept separate and run on their own levels. You can then mix them as needed. We talked about DAO's (data access objects) and using universal getters and setters to get at the data and the sub pieces of those concepts.

The guys were getting into what will and won't work and why. They were talking trade-offs of simplicity vs flexibility and other factors. Other topics ranged clear out to security, XSS (cross site scripting), SQL injections, etc. They were talking about transactional records, commits, roll-backs, try/catches, and other safety measures. They were talking table level locking, application flow, traffic, scalability, and usability.

They were talking about unit tests, global testing, and other pieces. Standalone tests, mock-ups, and sequence tests. Having their testing already ready and done really helps them to go in and change things with confidence. Test driven design and getting that peace of mind, knowing that you have a number of prebuilt and preselected tests to run on your old and new code. It is a real time saver and helps them have the confidence that things are working, even with changes.

We are changing the implementation (how things are done) vs the background core principles (why or what is being done). Pretty technical discussion. These guys are masters and are good at what they do.

We are trying to get the entire application out to the web/API socket level. We need a way to structure things and yet have modular data and open access to all.

After the demo/meeting we all split up and worked on our own projects. Steve, Alan, and Wayne kept working on some Metrc plant code. I was working on the developer's notebook project. Then after that, we jumped into a discussion about servers, virtual servers, and how to help optimize the different servers. We were talking heap sizes, through put, and other optimizing and server asset management options.