Response to the Williams Reading

    While reading Literacy and Computer Literacy: Analyzing the NRC's Being Fluent with Information Technology, I was intrigued by the layout of the research and documentation used by the author.  By starting with a list of themes the National Research Council (NRC) and itemizing what was and was not covered in their findings, I feel Kate did an excellent job at elaborating what all the technicality meant with relationship to the average person.  Though it did make the NRC's research look partially incomplete, I feel that the information Williams provides more than fills in the gaps left behind in the NRC's research. 
    In addition to providing good information about what computer literacy is, I feel Kate used a good example with engineers vs. lawyers with respect to technology each field requires.  Though I do not feel engineers and lawyers are the most polar opposite fields of study, the comparison did serve as a great tool to emphasize how diverse the digital world is becoming. Just like not everyone understands CAD programs or stress analysis software, there are many others who don't quite understand music software or Photoshop programs.  Though a student's major does not bar them from certain programs, (I am fairly interested in music mixing and alteration with software like Traktor Pro despite my mechanical engineer field) what a student is enrolled for does limit them to the software AVAILABLE to them (i.e. getting a CAD program for an engineering course).
    As stated in the Williams piece, this almost pre-determined availability of software makes it difficult for individuals to become fluent in different types of digital technology.  In addition to this, few software designers release trial versions of their products or release versions that have very limited capabilities until the "full" version is purchased.  When presented with tech-related challenges, many individuals seek outside help rather than take the problem on themselves.  Is this because they are not experienced with the required software or programs? Or is it the fear of learning a new skill at the risk of breaking the technology in the process?  Though the possibilities are endless, it appears that we are perfectly content to "let the pros do their jobs," while we observe and learn from a distance.
    Though this is only a portion of the topics covered in the Williams reading, Literacy and Computer Literacy: Analyzing the NRC's Being Fluent with Information Technology, it captured my attention and made me think about what it really means to be tech-literate.  If nothing else, this reading helped me better understand that the more programs and software I'm exposed to, the better prepared I will be when others are depending on me to fix something they don't understand.  From designing hydraulic systems for heavy equipment to mixing a new song, I am well on my way to becoming a go-to person for anyone with questions o the software I am familiarizing myself with.