No care Thursday
10-05-2017, 10:39 AM
#35
Still too rich for my blood.
Here are the specs
https://parts.subaru.com/p/Subaru__/...200277893.html
Here are the specs
https://parts.subaru.com/p/Subaru__/...200277893.html
10-05-2017, 11:15 AM
#37
Registered User
iTrader: (11)
Join Date: Jan 2008
Location: Cheesesteakville
Posts: 6,833
Car Info: 05 wrx wagon, 90 celica alltrac, 66 mustang
Had to pick up my mom at Miata Subaru and rescued a Chiwawa that was running around on 80. I was in the penskee truck towing the Justy.
10-05-2017, 11:29 AM
#39
Still too rich for my blood.
Here are the specs
https://parts.subaru.com/p/Subaru__/...200277893.html
Here are the specs
https://parts.subaru.com/p/Subaru__/...200277893.html
10-05-2017, 01:11 PM
#44
Call me Pebbles
iTrader: (11)
Join Date: Nov 2011
Location: I do all my own physics.
Posts: 5,908
Car Info: Moist
Two of the dumbest conversations I've had with co-workers on the same day, back to back, with two different people.
Conversation 1.
Co-worker 1: "This is bull****. Why do *we* (Licensing Section) need to review our policies and procedures? This should be the Regulations Unit's responsibility."
Me: "This has nothing to do with the regulations. These are licensing policies and procedures. Who better to review and update them than Licensing Staff?"
CW 1: "Yeah, but I still don't see why *we* have to do it. They should hire someone from Clerical or Support Staff to do this."
Me: "Do you really want a a non-technical person writing technical policies and procedures? We're the technical experts, we should write the technical policies and procedures."
CW 1: "Yeah, but this was supposed to be [name withheld, but another technical staff]'s responsibility."
Me: (laughing) "Do you really want to follow what [referenced technical staff] wrote down as the operational policy and procedure we will be following?"
CW 1: "Well, no, but she already wrote it. Why do I have to review it? I'm just going to print it out and sign it."
Me: (staring blankly, dumbfounded) "You don't want a non-tech writing your policies and procedures for you, but you don't think you, a tech, should write it. You don't want [referenced tech staff] to write it, but you don't want to review what they have written."
CW 1: "Yeah!"
I may have hit my head on my desk hard enough to give myself a concussion.
Conversation 2.
Co-worker 2: "Hey. Is [my subordinate] coming in today?"
Me: "No. They are out for [reason]. Why?"
CW 2: Oh. Well I've been sending him a bunch of emails trying to coordinate our site visit Tuesday, but he's not responding."
Me: "He's not responding because he's off--"
CW 2: "Well, it's a little frustrating because I won't see him before Tuesday and I'm trying to coordinate our meetup."
Me: "Did you try calling him on his cellphone?", pointing to the home/cell phone number list posted.
CW 2: "I don't want to bother him. I'll just try emailing him again."
Concussion #2.
Conversation 1.
Co-worker 1: "This is bull****. Why do *we* (Licensing Section) need to review our policies and procedures? This should be the Regulations Unit's responsibility."
Me: "This has nothing to do with the regulations. These are licensing policies and procedures. Who better to review and update them than Licensing Staff?"
CW 1: "Yeah, but I still don't see why *we* have to do it. They should hire someone from Clerical or Support Staff to do this."
Me: "Do you really want a a non-technical person writing technical policies and procedures? We're the technical experts, we should write the technical policies and procedures."
CW 1: "Yeah, but this was supposed to be [name withheld, but another technical staff]'s responsibility."
Me: (laughing) "Do you really want to follow what [referenced technical staff] wrote down as the operational policy and procedure we will be following?"
CW 1: "Well, no, but she already wrote it. Why do I have to review it? I'm just going to print it out and sign it."
Me: (staring blankly, dumbfounded) "You don't want a non-tech writing your policies and procedures for you, but you don't think you, a tech, should write it. You don't want [referenced tech staff] to write it, but you don't want to review what they have written."
CW 1: "Yeah!"
I may have hit my head on my desk hard enough to give myself a concussion.
Conversation 2.
Co-worker 2: "Hey. Is [my subordinate] coming in today?"
Me: "No. They are out for [reason]. Why?"
CW 2: Oh. Well I've been sending him a bunch of emails trying to coordinate our site visit Tuesday, but he's not responding."
Me: "He's not responding because he's off--"
CW 2: "Well, it's a little frustrating because I won't see him before Tuesday and I'm trying to coordinate our meetup."
Me: "Did you try calling him on his cellphone?", pointing to the home/cell phone number list posted.
CW 2: "I don't want to bother him. I'll just try emailing him again."
Concussion #2.