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 a GoToMeeting session with Nick and Alan. We started out the day by going over where each of us were at. Alan then gave us a small little lesson on some object oriented programming stuff that he is learning at school. Good stuff. Here is a small recap. - Encapsulation - like a cfc - like code goes together - functions and methods - keep things separate - logic goes together, display goes together, and data goes together - Keep things simple - what to put in and what to expect? - Cohesion - things that are similar stick together (keep like tasks together) - limited goals and range of functions - Coupling - how much (data or other pieces) goes between the calls and passing the data back and forth - the goal is to pass as little as possible but yet keep the trail going - Readability - make things consistent and easy to understand. for example: y="smith" (bad) vs. last_name="smith" (good) - They recommend a noun for variables (describe the what it is) and a verb for methods or functions (what does it do or how does it behave) - Only use plurals if really plural - otherwise use singular After the small lesson, we had a small session on what this means inside of adilas and how we could use similar things for objects and data over time. We did some drawing and setup models that show objects being built and manipulated over and through time. We then talked about budgeting and how you could set goals and budgets according to what you wanted to do. You could then compare the two. We then talked about how if the model is based over time (x-axis) and you were also capturing the up/down of the resources (y-axis) and also the stacking and spatial pieces of the puzzle (z-axis). You could get some great predictive models that through data could show visual stories of what is going on and/or what we would like to have happen. Fun session. One more small note about time... It goes in both directions as far as we know. Backwards and forwards. That makes it a great base to build on. See and search other notes about the 3D timelines and 3D calendars in the developer's notebook. Steve came on and we talked about a server error that was on the server yesterday. There was an error with one little letter. We then pushed up the code and didn't check it. We shut down the servers for about 20 minutes. Steve was comparing the system to the human body. If we are in the vital pieces (heart, brain, lungs, etc.). Maybe push things to a single server and then fully test things. We need to setup some standard procedure and/or procedures. We also talked about not forcing things. If needed, we could always push things to another session. We also need a calling tree and line of authority of who can fix what and what to do. There is another need for communication back to our clients. It is fun and kinda crazy to create this music and symphony. It is never done and it keeps going. Sometimes we are realizing dreams and other times we are pulling out our hair. It is both addicting and frustrating at the same time. Keep building and searching for the bliss. What a mix of highs, lows, joy, happiness, depression, anxiety, funk, pleasure, purpose, vision, etc.. What a random ride... We are nothing without each other. The sum of the blocks make up the tower. |