Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
|
Sorry, no photos available for this element of time.
|
|
Uploaded Media/Content & Other Files
(1)
|
||||
Media Name | File Type | Date | Description | |
code_sign_off_ideas.docx | Doc/Text | 8/12/2020 | This is a self checklist on doing code sign-off and recommendations for coding, validation, and naming conventions inside of the adilas.biz environment. Parts of this document will end up in Chuck's adilas docs project (online web pages with the information organized and centrally located for ease of use and consistency. |
Notes:
|
To start out with, Chuck and I were on by ourselves at the beginning. We went over some settings and ways to configure some of the email options from inside of adilas. After that, Chuck reported on some of his current projects. The later half of the meeting was somewhat of a group meeting. We had Russell, Alan, Chuck, Wayne, and myself on the meeting. The subject was dealing with internal documents and what is needed, wanted, and required. We covered code sign-off, frontend style guides, backend suggestions, and other protocols. Alan is going to produce a document dealing with the backend and database access structure. This will end up having outlines of our framework and dealing with pages calling services and services calling DAO's (database access objects) and those DAO's reporting back to the services and then back to the pages. Wayne and Chuck (combo) will be creating and producing some test driven design docs and processes. Wayne requested Chuck's help to help with the actual writing and verbage. Wayne will show Chuck and Chuck will do the technical writing stuff. See attached for a copy of some older work on some code sign-off ideas. This is more of a flavor vs a hard fast set of rules. |