crazy?
In my internet class (intro to management information systems DATA) each student is given 84 tasks to complete with software developed by SAM.
Over a period of about 3 weeks, I completed 38 of 84. However, when I went to start working on them again on Wednesday (2 days before they are due) I found out that the SAM server had a crash and all of my tasks were deleted. I went to the lab library as soon as possible. At 7:46 pm I started over from scratch. The lab computer is slow, the work is lame, and the software leaves much to be desired. However, after 1 hour and 8 minutes, I finished the assignment. I started to upload the files to the SAM server....and **thud** I'm not really sure what the thud was. It could have been:
a) my heart dropping
b) the sound of me pushing the monitor off of the desk in my 2 second day dream
c) me getting up and pushing the chair into the desk as I walked out of the library in disgust
Regardless, I came back to the computer, hoping that it was untrue, but knowing good and well that all of the information was lost in the transfer. As I stared at the screen, I contemplated my hatred for SAM and any other incompetent businesses, but realized that it was time for a decision. I had 1 hour and 6 minutes left, 2 minutes less than it took me to do the assignment the last time. I then decided to email my professor to inform him of my current computer misfortunes so that he might be considerate when I fail to turn it in.
After emailing professor Sears, it dawned on me: this ridiculous sub-par program deserved to be conquered as a cheetah would quickly hunt and slaughter a baby gazelle. I quickly logged back into the program, and began on task #1. This time, however, I was not going to abide by the laymen's rules of the training. I would do things my way. I was working as fast as the lab's outdated computer would allow me to. Using shortcuts and hotkeys, I finished each task. After a short time period, I was working on task #30. I saved my work and printed it off as evidence of my progress. Again I saved at #50 and #70. These reports were proof of SAM's inefficiency, lack of knowledge they possess on their own subject, and general immaturity as a software production company. Simultaneously SAM raised the white flag as I finished task #84. I quickly uploaded my files and printed my last report.
**After completing the assignment I checked the productivity of the rest of the students. Of course, everyone had already turned their assignments in, but how long did it take them? I was very curious. *click, click, click click* I found it. 6 hours and 38 minutes. That's what I thought. How about 22 minutes. Ya, that sounds about right.
22 minutes = actual assignment time + printing time + login time
My way was 18 times more efficient than SAM's way. Shocking...
Over a period of about 3 weeks, I completed 38 of 84. However, when I went to start working on them again on Wednesday (2 days before they are due) I found out that the SAM server had a crash and all of my tasks were deleted. I went to the lab library as soon as possible. At 7:46 pm I started over from scratch. The lab computer is slow, the work is lame, and the software leaves much to be desired. However, after 1 hour and 8 minutes, I finished the assignment. I started to upload the files to the SAM server....and **thud** I'm not really sure what the thud was. It could have been:
a) my heart dropping
b) the sound of me pushing the monitor off of the desk in my 2 second day dream
c) me getting up and pushing the chair into the desk as I walked out of the library in disgust
Regardless, I came back to the computer, hoping that it was untrue, but knowing good and well that all of the information was lost in the transfer. As I stared at the screen, I contemplated my hatred for SAM and any other incompetent businesses, but realized that it was time for a decision. I had 1 hour and 6 minutes left, 2 minutes less than it took me to do the assignment the last time. I then decided to email my professor to inform him of my current computer misfortunes so that he might be considerate when I fail to turn it in.
After emailing professor Sears, it dawned on me: this ridiculous sub-par program deserved to be conquered as a cheetah would quickly hunt and slaughter a baby gazelle. I quickly logged back into the program, and began on task #1. This time, however, I was not going to abide by the laymen's rules of the training. I would do things my way. I was working as fast as the lab's outdated computer would allow me to. Using shortcuts and hotkeys, I finished each task. After a short time period, I was working on task #30. I saved my work and printed it off as evidence of my progress. Again I saved at #50 and #70. These reports were proof of SAM's inefficiency, lack of knowledge they possess on their own subject, and general immaturity as a software production company. Simultaneously SAM raised the white flag as I finished task #84. I quickly uploaded my files and printed my last report.
**After completing the assignment I checked the productivity of the rest of the students. Of course, everyone had already turned their assignments in, but how long did it take them? I was very curious. *click, click, click click* I found it. 6 hours and 38 minutes. That's what I thought. How about 22 minutes. Ya, that sounds about right.
22 minutes = actual assignment time + printing time + login time
My way was 18 times more efficient than SAM's way. Shocking...
posted by jtw at 8:00 AM
1 Comments:
oh josh...it's things like that that make you my hero.
i am so proud of you!!
we neeeeeed to hang out...
<3 kells
Post a Comment
<< Home