Customers Suck!

Customers Suck! (http://www.customerssuck.com/board/index.php)
-   Unsupportable (http://www.customerssuck.com/board/forumdisplay.php?f=29)
-   -   When you're more competent than the teacher (http://www.customerssuck.com/board/showthread.php?t=115914)

Aragarthiel 10-05-2016 01:59 PM

When you're more competent than the teacher
 
I'm currently sitting in my Mobile App Development Class. Don't judge, I've already finished my work for the day and am waiting for the teacher to catch up so she can take attendance and I can leave.

Why does the teacher need to catch up with me? Well, because she can't follow basic instructions.

This class is Java based, and having not taken any Java courses, I don't have much of a clue what I'm doing. However, I can follow basic instructions. How basic? Here's an example:
Quote:

type protected void onListItemClick(ListView l, View v, int position, long id)
Most of the instructions we're using are just like that, telling us exactly what to do. And somehow, this woman who's been supposedly doing this for years, manages to screw that up. Either she skips entire steps, misspells something, or just can't read the screen well enough to figure out what the error is. I get this done faster by just reading the textbook and following instructions on my own.

Oy. :headdesk:

mjr 10-05-2016 04:38 PM

You'll run into that in the real world too. Believe me.

wolfie 10-05-2016 10:23 PM

I had a similar situation in a CAD class while I was studying for machine shop.

gerund 10-08-2016 07:57 AM

I had a teacher in the local tertiary institution who was teaching us Linux. I am a Unix administrator and have done "Train the Trainer" courses in Unix (not Linux) and I was doing the course so I could get a Diploma in computer science.

Snippets from the class:-

T - Teacher
M - Not the teacher

T: So this is the directory ETC (pronouncing it Et-Sa).
M: Isn't is etcetera?
T: No no, you don't know much about Unix, do you?
M: It's always been called etcetera.
T: In Linux it's "et-sa"
M:...

T: So a file can be called anything in Linux.
M: Can the file be called "-rf"?
(Note this is well known to experienced Unix admins as that is an option for the removal program "rm" so you could never remove a file called "-rf" with rm.)
T: Yes!
(All sorts of emotions cross his face as he thinks it through)
T: Er... no I don't think so.
M: So a file can't be called anything?
T: There are some limitations.
M: Can a file be called "*"?
T: (Exasperated) No.
M: Can a file be called "-"?
T: ...
M: What about "?"?

Racket_Man 10-08-2016 09:28 AM

Quote:

Quoth gerund (Post 1330493)
T: So this is the directory ETC (pronouncing it Et-Sa).
M: Isn't is etcetera?
T: No no, you don't know much about Unix, do you?
M: It's always been called etcetera.
T: In Linux it's "et-sa"

I was taught yes the directory was etcetera (etc for short) and pronounced Et-Se (hard e not soft a)

but this might be some "regional" thing so a matter of semantics and pronunciation

gerund 10-08-2016 09:54 AM

Quote:

Quoth Racket_Man (Post 1330501)
pronounced Et-Se (hard e not soft a)
but this might be some "regional" thing so a matter of semantics and pronunciation

Listen to the sound byte here

The Unix and Linux directory /ETC has always been the shortened form of "et cetera"

prjkt 10-08-2016 12:57 PM

heh. I remember being "trained" on a photo lab system by someone hired by the lowest bidder.
Not the trainers fault, she was just told to read off the script, but it was funny to see her trying to press the brightness up button on the monitor to turn the sound out, forcing me to just reach over and rotate the volume knob about 3cm to the left of said buttons

MadMike 10-08-2016 05:59 PM

This is going WAY back, but where I went to school, they made everyone take a course in BASIC, even the people who weren't there to take computer courses. The whole thing was pretty useless in my opinion. If you were a computer person, chances were you already knew BASIC. And if you weren't a computer person, the whole thing could be pretty confusing.

One of my friends, who was a non-computer person, and always having trouble with it, always came to me for help instead of the teacher, mainly because everything he tried to tell her went right over her head. One day, I was sitting in the classroom doing nothing, because my programming assignment had been finished a long time ago. My friend came in from the lab and asked me if I could take a look at her program, which she was still having trouble with. I followed her into the lab, and the teacher followed both of us.

She showed me her program listing and told me, "I made these changes to it, and it's still not working!" I took one look at it and said, "Well that's not right! What idiot told you to do that?"

As soon as I said that, the teacher quickly turned around and left the lab. I looked at my friend, she just nodded her head, and then we both started laughing.

Quote:

Quoth gerund (Post 1330493)
T: So a file can be called anything in Linux.

That reminds me of something another teacher said when I was taking COBOL (once again, going way back.) Some of us were confused by the paragraph names in the sample program listings from the book, and he told us, "You don't have to call it that. You can call it anything you want. You could call it 'Horse Shit' if you really wanted to, but please don't."

Deserted 10-09-2016 07:03 PM

Quote:

Quoth gerund (Post 1330493)
M: Can the file be called "-rf"?
M: Can a file be called "*"?
M: Can a file be called "-"?
M: What about "?"?

The answer to all of those is "yes". You just have to jump through some hoops:
Quote:

$ touch \*
$ touch \?
$ touch -- -rf
$ echo "" > -
$ ls -l
total 4
-rw-r--r-- 1 deserted users 0 Oct 9 10:45 *
-rw-r--r-- 1 deserted users 1 Oct 9 10:46 -
-rw-r--r-- 1 deserted users 0 Oct 9 10:45 -rf
-rw-r--r-- 1 deserted users 0 Oct 9 10:45 ?

So yes, it's possible... but usually not a good idea.

gerund 10-10-2016 02:26 AM

Quote:

Quoth Deserted (Post 1330622)
The answer to all of those is "yes". You just have to jump through some hoops:


So yes, it's possible... but usually not a good idea.

But that's the point of my story. I knew files could be created in those names, because in my career as a Unix administrator I had come across files called that. I had to devise a way to delete those files because they could not be accessed but the normal everyday programs we used like "vi" and "rm" and "mv" or "tar".

The teacher was supposed to teach us Linux and he had no idea that files could be named that and (obviously) had never seen those files in real life or tried to do anything with them.

As far as it not being a good idea, have you ever seen a whole nights backup fail because of a file called "-"? Not only is hard to find why the backup failed, it's then really hard to remove that file. I think I finally settled on "rm -i *" and then hitting the "n" key about a hundred times and "y" once. :D

BTW I knew I was being annoying to the teacher but it was because he constantly annoyed me with his obvious lack of knowledge and his lack of enough self-awareness that he did not have the knowledge.


All times are GMT. The time now is 10:13 AM.

Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2019, vBulletin Solutions, Inc.