After the fact
Completing this assignment was surprisingly time-consuming (and kind of frusterating), in part because I had no experience with screencasting or video editing, but also because, despite the fact that I had to describe my workflow in writing for the previous assignment, I didn't really have a true workflow which could easily be emulated in the screencast. That said, learning to show what I did when I worked--especially in a concise way that other people could watch, learn from (perhaps), and understand--rather than simply describe it, ended up being a really useful exercise insofar as it forced me to truly develop a more consistent system of working that could be exhibited, and thus, also be mimicked--even by myself. In this way, having to develop a workflow to exhibit for this assignment resulted in a system I now use to perform my own work. And so, while there was something aritificial about having to develop and exhibit a workflow I had never really used, this exercise made my actual working-life more productive and efficient as I became the pupil of my own process. There is, of course, sometimes nothing more educational than teaching itself.
When I came back to edit this assignment for the book, I had a more sophisticated understanding of how to use Scalar and decided to move what had been a long series of bullet points describing my workflow in the first version into annotations that correspond with what is happening in the video. Scalar's various options for how content can be viewed (and written) made the editing process interesting and productive. Commenting on my workflow using annotions rather than a page of bullet points allowed the digital object (my workflow video) to become the central content of the assignment, as opposed to the writing. The assignment reads rmuch differently as a video which is annotated than it once did as a description of my workflow accompanied by a video.
Author: Emily Smith
Word Count: 324
When I came back to edit this assignment for the book, I had a more sophisticated understanding of how to use Scalar and decided to move what had been a long series of bullet points describing my workflow in the first version into annotations that correspond with what is happening in the video. Scalar's various options for how content can be viewed (and written) made the editing process interesting and productive. Commenting on my workflow using annotions rather than a page of bullet points allowed the digital object (my workflow video) to become the central content of the assignment, as opposed to the writing. The assignment reads rmuch differently as a video which is annotated than it once did as a description of my workflow accompanied by a video.
Author: Emily Smith
Word Count: 324
This page comments on:
Flowmotion (27 August 2012)
Previous page on path | Commentary, page 4 of 23 | Next page on path |
Discussion of "After the fact"
Add your voice to this discussion.
Checking your signed in status ...