Slashdot Mirror
Your Worst IT Workshop?
suntory writes "I am a lecturer at a Spanish university. This week had to attend a workshop on 'Advanced HTML and CSS' for the university staff. Some of the ideas that the presenter (a fellow lecturer) shared with us: IE is the only browser that follows standards; frames and tables are the best way to organize your website; you can view the source for most CSS, Javascript and HTML files, so you can freely copy and paste what you feel like — the Internet is free you know; same applies for images, if you can see them in Google Images Search, then you can use them for your projects. Of course, the workshop turned out to be a complete disaster and a waste of time. So I was wondering what other similar experiences you have had, and what was your worst IT workshop?"
I've GIVEN some great, and somewhat bad talks in my day - every good speaker will tell you the same thing.
Most of the bad talks were situations where I was asked to sub for someone - or an area where I "WANTED" to be an expert - but really wasn't.
Many times, after a talk, I find that something I said was just plain wrong - it happens - to everyone - even the best speakers out there.
They key is, as an attendee, to not sit around and waste time listening to a bad speaker. I just quietly walk out, picking up an evaluation form in the process, and making sure the instructor gets my feedback.
As an occasional bad speaker - the best thing an audience member can do for me is to let me know if I have gotten it wrong! In the end, the only way tp turn a bad speaker into a good one - is through feedback - even if it is "YOU SUCK!"
I'm attending a course on web design in my college this semester.
The TA that's giving the lectures:
However, two years ago I took a course given by a guy who told a friend of mine "Stop surfing the internet! Or else you won't know how to use Internet Explorer!" (yeah, it loses a bit in translation).
He could spend two hours explaining how to navigate to a bloody webpage from IE 6. And then how to add a crappy link to whatever IE calls bookmarks.
And when I said "could", I mean "did".
Repeatedly.
By the FSM's noodly appendage, I wish I was making this crap up.
Ignore this signature. By order.
I took the advanced C++ class at my university the first quarter after they made the class transition from Pascal. I had prior work experience as a C++ programmer, so I figured it would be an easy A. Boy, was I wrong!
The professor was like 80 years old. He must have been around before they developed the one in binary and only had zeros. That in itself isn't so bad, except that he didn't bother to even crack the book to teach C++. He'd give examples and try to work problems on the whiteboard in some kind of pseudo language that wasn't Pascal, definitely wasn't C++, and that hopelessly confused the students who didn't have a really good grasp of the language. Oh, it gets better, though.
His TA, the girl who graded our labs, knew even less. We had a lab where we had to implement a complex number class, ho hum. The instructions stated that we had to develop methods to do things like add, subtract, multiply, divide, etc. complex numbers, but they didn't explicitly state what we had to call our functions.
Any C++ programmer worth anything would know that the obvious thing to do is to overload the +, -, *, and / operators so that they could accept complex number arguments and return the appropriate result. I spent a few hours working on it, churned out my class, and when I got the lab back, she had failed me!
I asked why she gave me an F, and she explained that I was supposed to implement the functions using names like add, subtract, etc. I told her that that was nowhere in the instructions for the lab, and she admitted that it was okay to use other function names, but operator overloading was a no-no. Of course, I asked why, and her answer—I kid you not—was that because if you overloaded the operators, other programmers wouldn't be able to tell the difference between your class and built-in types. I argued vehemently that that was the point of operator overloading, that it was an extremely common practice in C++, but she wouldn't be convinced.
It was toward the end of the semester, so I took the lab to my professor and explained to him what was going on. I even took a C++ best practices book with me to show what I was talking about and to prove that I'm not some crackpot stupid student trying to eek out a few extra points. The professor proceeded to explain to me that the university had just informed him that they were letting him go after the semester, that they were firing him. (His words exactly, not mine.) He said that if I had a problem with my grade, I needed to take it up with the TA, because he wasn't going to override anything she said.
In all the programming classes I took at the university, that was the only one in which I got a B, and I was absolutely furious. Not so much because of the negligible impact to my GPA, but because it's the only time I've ever gotten a grade that I truly felt like I didn't deserve, and it was all because of an idiot professor who didn't give a damn about anything (gee, I wonder why they fired him) and a TA who didn't know crap about the subject that she was grading us on.
It's too bad, too. All of my other experiences at the university were relatively pleasant, and I'm a life member of the alumni association today. But that one incident still sticks in my mind as the height of stupidity. I wish now that I had had the balls to escalate it to the dean or maybe even higher. I can't help but wonder how many students failed or otherwise did miserably in that class because of him, and I can't help but wonder if any of them gave up computer science because of that bad experience. God, I hope not.