Misc. Notes 31 March Reflections

Transcribed from hand-written notes-

Post-23-26 March trip

·         Complexities of software take much time & experience to fully understand

·         System limitations should be confronted, understood and time taken to evaluate and plan for (problems with)

31 March Class notes: 

I can mention in my writing, my biases (i.e. I’m very passionate about what I am training others to use)

Re: Presentation – can use metaphors to identify a point or to underscore a topic.   In Intro, I can mention the long overall AR scope, but mention that I will cover the last 7 months only.

Re: Measurement – quantifying: I can take a conversation & assign a scale of values to it (or them), to aid in displaying importance

31 March Reflections:

I got full buy-in from work to present ‘problem’ to students next week.  My work is behind this (they were very skeptical at first until I used some school-voodoo-science ‘Learning’ discussion points).  Overall they seem excited at seeing what they (students) come up with for resolutions.

Emphasis on process identification-so students have something useful to take, study, and grow from.  Essentially they will create their own artifact that they will have to use for future problems, anomalies, or issues.