Becoming Producers of
Summer 2, 2013
Two major jobs for the week
• Complete a simple, basic
computer command-related task
• Document, analyse and write-up
the learning and interactions that
take place while learning what the
task means and how to do it
Documenting your group’s activity
• Closely observe what’s going on and keep
fieldnotes (observed data)
• Make note of the documents you use to help
you (written data)
• Take photographs (observed data)
• Make video and audio recordings (spoken
• Screen recordings and screen grabs (observed
• Make note of the people you use to help you
(inside and outside your group)
Good fieldnotes are:
• As descriptively detailed as possible:
–Mud maps of space layout etc.
• As objective as possible (avoid
interpretations as far as is possible)
Writing good field notes
• Develop your own shorthand
• Include regular time stamps
• Leave a wide right-hand margin
• Ensure they’re legible for others
• Detail, detail, detail
Not nearly enough detail.
We finally found a tutorial for
line prompts. Yay!
10:41am Stacey used Google.com to search for
the phrase “command line prompt” + tutorial. The
search returned 1million + results. We clicked on
the third search return—David
is—because Leanne had seen Baumgold’s website
recommended on wikipedia entry for “command
Leanne: “Hey, click on the third one. Baum-whats-
Stacey: Why that one?
Leanne It was in the wikipedia bibliography.
Stacey clicks on the URL and opens the page……..
Use Windows command
prompts to make your
computer “do” something
Danger, Will Robinson!!
Do NOT run a command just to see
what it does.
“Make sure you understand what the
command is supposed to do first, especially
is the command involves changing or