Unit 2 Cruising through the command interface

Playing with the system was an interesting venture.  As I was first going through the tutorials and messing with the virtual desktop terminal I was reminded of my old gaming days when I used to MUD or play early text based games.  All one needed to know were basic commands to tell the game or computer what you were doing.  Seems simple enough.  As I read through the tutorials, several of the items reminded me of the MARC record, so it was not complete gibberish to me.  I feel like I am relearning a language that I sorta picked up years ago, but was never completely proficient in.
I took the tutorials one step at a time, read, skimmed, re-read certain parts.  My eyes glazed over for certain sections.  It was necessary for me to actually try things and play with the machine rather than just read the text. A lot of the words ran together or caused me to question the meaning.  There are a lot of commands to remember... I am thinking I might need to buy a book to help me with easy access to commands. It is easy to understand basic concepts, but harder to get a grasp on the fine details of the commands. My intent is to keep skimming the tutorial, and then go back to it as I actually try to do more things in the virtual machine. Compared to how quickly I normally navigate through my computer, this is pretty slow and cumbersome for me.  This really is a lot like learning a new language.

Words to look up:

shell
bash
bin
.cmd
root

Unit One

First of all it is interesting to read the strange lingo and odd mannerisms that appear on this forum.  Definitely need to do a cultural immersion to fit in to this site.

I was scrolling through the random questions when I noticed the sticky thread that was tacked to the top of the discussion.  Hmmm, I bet they are useful.  So I went through the "LINUX Command Line Learning Resources" posts.  There are several links to help guide us through some actual coding.  I noticed some of them indicate a lot of people cut and paste code instead of memorise it.  I had heard this before so it seems pretty accurate.  I think it would be useful to memorise though, if it breaks how will you fix it if you always cut and paste?  You wouldn't know how it works.
Also found a list of keyboard shortcuts  those are always handy when working on computers.

Words to look up:

GUI
CLI
Unity
Command File Extension (command line)


Feeling in over my head.

Week One

Blog post

So far it has been smooth sailing.  When I heard it would take a while to download the Ubuntu desktop and server program I thought to myself, “Does it really take that long?  Pshaw.”  Well, oddly enough it did take 30 minutes.  I would say that this is a sign of how inexperienced I am when it comes to this side of technology.

As far as the reading, oh my.  I have a lot of work ahead of me.  It is very much like trying to understand a foreign language.  I am looking forward to some hands on projects that will help me make sense of the words and apply a word to an action.

Here is a list of words that I have had to look up:

TCP/IP

kernel

GNU

compiler

So far I am trying to not overwhelm myself with the vocabulary.  About to start week 2, hopefully I am not so slow this week.

DigIn.... dig it.

Hello,
My name is Kelee and this is my introductory post for the Intro to Applied Technology course that I am taking as I pursue a master's in library science.  I have very little experience with applied technology.  I use computers and I rarely break them. I can usually troubleshoot most computer issues, but rarely know HOW.  I use the trial and error method of solving problems.  I secretly believe myself to be a computer genius based on this experience.  I am hoping this class will not break my little computer genius bubble, but perhaps it would be good to get a little modesty fed to me as I struggle through assignments.  That being said, I am about to embark on the first weeks assignments.  We shall see what the future will hold.