Oh, by the way....
Feb. 20th, 2011 04:05 amI forgot to mention, I graduated with a BS in Computer Science in December, and I'm currently following up with a BS in Electrical Engineering! I'll never have to swap out a Winmodem again!
(obligatory rant for topicality: the preceding involved a 78-day paper chase when it was discovered that the automated "apply for fall graduation" web form failed silently, despite the student database reporting was expected to graduate on time. "Oh, that doesn't mean anything, that's just what the computer says. We don't have the staff to check up on everyone who is supposed to graduate and doesn't apply.")
Now, back to that artificial brain...
(obligatory rant for topicality: the preceding involved a 78-day paper chase when it was discovered that the automated "apply for fall graduation" web form failed silently, despite the student database reporting was expected to graduate on time. "Oh, that doesn't mean anything, that's just what the computer says. We don't have the staff to check up on everyone who is supposed to graduate and doesn't apply.")
Now, back to that artificial brain...
no subject
Date: 2011-02-20 06:05 pm (UTC)no subject
Date: 2011-02-20 08:23 pm (UTC)When I was supposed to graduate, I called in to the registrar to verify everything and the person on the phone came back with "Sorry, your file isn't here?" and I was like "?!?! what does that mean, you don't have my records?" "No, the registrar [meaning the actual person with that title] check it out to verify it, it is probably home with her." I'm still amazed that such a thing is/was even possible.
As it turns out, the relatively new database system was set of "fail first." It wasn't looking for some set of courses that would allow you to graduate, it accepted any assignment of your courses that didn't result in a diploma as a reason not to give you one. I'd taken some courses required for EEs, but not all of them, which is obviously more significant than having taken all the courses required to graduate as a software engineer, according to their database.
no subject
Date: 2011-02-20 08:31 pm (UTC)no subject
Date: 2011-02-20 08:42 pm (UTC)no subject
Date: 2011-02-20 08:49 pm (UTC)no subject
Date: 2011-02-21 11:43 am (UTC)no subject
Date: 2011-02-21 03:36 pm (UTC)Trust no one.
no subject
Date: 2011-02-22 01:40 am (UTC)I've also found that "No." (just the one word, by itself) is a fantastic phrase for using on people who spend most of their lives wearing a groove in a behavioural template for a job. It's the fastest way to throw someone off-track and into a mental trainwreck, particularly if they keep making assumptions.
It shouldn't be "No," followed by an explanation. It shouldn't be "No, that isn't right," or "No, listen to me, dammit!" It should just be "No." It makes them eventually throw a rod and have to ask "Well, what, then?", and it's only then that they start to listen. (If they slide back into the comfortable template, the process can repeat a few times.)
ParTICularly satisfying on calls which are "recorded for training purposes", because it's them stumbling headlong into one conversational pothole after another, with me doing nothing but use one-syllable words to tell them they're getting their job wrong.
no subject
Date: 2011-03-18 04:33 am (UTC)