all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
Yellow
|
|
|
Sorry, no photos available for this element of time.
|
|
|
|
Notes:
|
|
On the morning GoToMeeting session with Steve. We were talking about progression and where things are going. In order to keep progressing... we need to keep focusing on keeping data, logic, and display in separate containers. That way we could mix and blend them as needed. We were talking about the word "fracture" and how we keep seeing things fracture and spread. It is amazing to see how deep some of the fractures go and how everything keeps breaking into subs. adilas - all data is live and searchable - Database - What does that include? Table design, schema, the map, layout, data structure, relationships, organization, data types, queries, storage containers, options, settings, permissions, standard usage, custom needs. - Logic - What does that include? Objects, decisions, flow charts, conditions, cases, and tons of different options based off of data or flow. The logic is the binder between the data and the display. Without the logic, the data wouldn't mean anything and the display wouldn't know how to look or what to do (function). The logic needs to be a blend of static, dynamic, and mixed values based on where it lives and what it does. I think it would be a big mistake to force everything into a perfect box... yes, that might help in places, but it would also create all kinds of random things as well as things that just did and/or don't fit. We need to be flexible on all fronts. We will end up needing standard settings, custom settings, logic switches, toggles, choices, and ports that allow for custom everything (black box stuff). - Display - What does that include? The display is what is seen and/or presented. It both guides the user on the inputs made and also requests and/or makes options available to the users. This is the user level. Displays need to be flexible yet consistent. Displays may be extended into interfaces. Interfaces show options, navigation, results, searches, adds, edits, deletes, updates, details, groups, etc. This could go on and on and has multiple faces and personalities. The display and/or interface goes from the surface clear down to the tiniest nut and bolt. This is how we get data in and out of the database based on the logic that is presented. - The Mix - You have to have all three pieces. If you are missing the container (data and database), the rules (logic), or what it looks like (display/interface), you don't have much. If you could mix and blend to get all three in a way that is powerful, pretty, and easy... then you have something. After Steve and I talked, I spent the rest of the session working with Bryan and going over a new 3rd party API socket. We did a lot of testing and restructured the output and info. We also had Eric chime in and we chatted about consistency and coordinating multiple developers on a single project. We have a couple of guys that are lightly stepping on some toes. Nothing intentional, just clients asking for mixed projects between multiple parties. No one knows who is doing what or what dependencies exist. |