Brahma
Obi-Bro Kenobi-X
- 12,642
- 47,189
Yep. There is a gig right down the street from where I will be moving. (Bought a house). I qualify for 80% of what they asking. The other 20% I never even heard of, never mind actually know.
- 2
How to handle a bad VP
- Thread starter Brahma
- Start date
-
Guest, it's time once again for the massively important and exciting FoH Asshat Tournament!
Go here and give us your nominations!Who's been the biggest Asshat in the last year? Give us your worst ones!
Yep. There is a gig right down the street from where I will be moving. (Bought a house). I qualify for 80% of what they asking. The other 20% I never even heard of, never mind actually know.
moonarchia
The Scientific Shitlord
- 24,260
- 45,542
Brahma
Obi-Bro Kenobi-X
- 12,642
- 47,189
Usually Hoshkar is the cause of a bad VP, His AE DD and Slow can cripple a raid with lots of Melee in it and one shot casters. The best thing to do is pull Hoshkar out of his lair and down the ramp towards the entrance, From there you can wedge him in the wall with the healers hiding behind it.
From there it's just a matter of doing ins and outs on his 12 second AE and burning him down.
He is weak to fire.
Once he's done VP is usually a cake walk with Nexonna the only other dragon giving you issues.
From there it's just a matter of doing ins and outs on his 12 second AE and burning him down.
He is weak to fire.
Once he's done VP is usually a cake walk with Nexonna the only other dragon giving you issues.
- 6
- 3
- 2
OU Ariakas
Diet Dr. Pepper Enjoyer
- 7,428
- 20,993
Ever thought about becoming an Avaya implementation engineer at a local or national Avaya re-seller? I'm sure you could make bank doing that.
- 1
Vinen
God is dead
- 2,791
- 497
Isn't Avaya spiraling down the drain? I'd recommend learning another companies technologies.
- 2
OU Ariakas
Diet Dr. Pepper Enjoyer
- 7,428
- 20,993
Haha, I almost typed that he needs to learn Cisco Telephony (UC) or switching from the other guy and then use that to become a Cisco delivery engineer since he is guaranteed work for the foreseeable future and Avaya just went bankrupt. Seriously
Brahma
, if you are within 10 years of retirement you might be fine; but I already see Avaya clients fleeing to Cisco or MyTel because of the uncertanty around their future. Worst case is one of the giants like Dell/EMC or a Nortel buys them in a fire sale.- 1
- 1
sakkath
Trakanon Raider
- 1,779
- 1,097
Was thinking the same thing when I first saw Avaya mentioned. Although I still have to power up Business Element Manager and Avaya Site Administration now and then we have mostly moved to CUCM. Wouldn't expect Avaya to be bought up by Nortel though since Nortel went bankrupt years ago and most of their tech was acquired by Avaya... Pretty sure what's left of Nortel is still being sued by the canadian govt.Haha, I almost typed that he needs to learn Cisco Telephony (UC) or switching from the other guy and then use that to become a Cisco delivery engineer since he is guaranteed work for the foreseeable future and Avaya just went bankrupt. Seriously
- 2
- 6,051
- 6,036
Ironically, I'm typing this from the old Nortel campus, which is now owned by the Government of Canada. Nice place. I worked here during their heyday in the mid-90s and it still looks almost exactly the same.
The case against Nortel (in the US and Canada, anyway) was over in early 2017. It was the largest chapter 11 case in Canadian history.
- 2
OU Ariakas
Diet Dr. Pepper Enjoyer
- 7,428
- 20,993
You are right. My mind was thinking Motorola while I was typing Nortel for some reason.
- 1
SuperNaught
Trakanon Raider
- 417
- 1,403
I have this atrophied place in my brain storing useless bits of information on Nortel AN and ASN routers. Excuse me, I just threw up a little in my mouth...
- 1
Brahma
Obi-Bro Kenobi-X
- 12,642
- 47,189
Sorry for the necro:
Going into a meeting in 30 minutes. I have a co-worker that has the same title as me, but his skill level is a couple notches below mine. He caused a major outage because of his laziness. (estimated a few million lost) During my RCA I figured out what and who the problem was. IF I call him out he might get fired. If I don't call him out I am blatantly lying, and my co-workers will know I am lying, because my RCA won't make sense. I then need to worry about someone going back to my VP with this analysis.
I do NOT like this guy for professional reasons. But he's a good person.
I call him out my team will see me as a sell out?
I am NOT a person to fuck with peoples careers or money this way. But I do my job when told. I try and be professional.
Quick thoughts?
Going into a meeting in 30 minutes. I have a co-worker that has the same title as me, but his skill level is a couple notches below mine. He caused a major outage because of his laziness. (estimated a few million lost) During my RCA I figured out what and who the problem was. IF I call him out he might get fired. If I don't call him out I am blatantly lying, and my co-workers will know I am lying, because my RCA won't make sense. I then need to worry about someone going back to my VP with this analysis.
I do NOT like this guy for professional reasons. But he's a good person.
I call him out my team will see me as a sell out?
I am NOT a person to fuck with peoples careers or money this way. But I do my job when told. I try and be professional.
Quick thoughts?
- 2
zzeris
King Turd of Shit Hill
- 20,528
- 87,655
Call him out and you said the reasons. As a professional, you are expected to be competent, right? Not cause a major outage because of laziness? If he gets away with it this time, there will be another time you have to cover his messes. The company won't be thankful you covered for a huge loss if discovered by others and shit always comes out.
- 2
Flobee
Vyemm Raider
- 2,686
- 3,092
IMO explain the situation exactly as it happened. Provide the name when asked but don't dwell on it. I always take the approach of 'shit happens' when dealing with outages and explaining to superiors. I always try to focus on resolution and future steps to prevent it from happening again. It is their decision as to whether or not they need to come down on this guy, not yours. In my experience if you report without judgement, you'll be fine. If he's incompetent it should come out in the problem/resolution description without you blatantly pointing a finger.
Depends on the culture though I imagine
- 6
Loser Araysar
Chief Russia Reporter. Stock Pals CEO. Head of AI.
- 81,093
- 162,276
Call him out for sure.
Your reputation as a professional is the most important thing here. That's what builds better teams, not covering up for incompetents.
edit: I just realized my post might have come across as aggressive after reading
Flobee
's post. I agree with
Flobee
. I would explain the issue and who caused it, but I wouldnt aggressively try to center it on him. No need to appear vindictive. Just provide info and responsible party and let your bosses figure out what they want to do
Your reputation as a professional is the most important thing here. That's what builds better teams, not covering up for incompetents.
edit: I just realized my post might have come across as aggressive after reading
Flobee
's post. I agree with
Flobee
. I would explain the issue and who caused it, but I wouldnt aggressively try to center it on him. No need to appear vindictive. Just provide info and responsible party and let your bosses figure out what they want to do- 3
Soygen
The Dirty Dozen For the Price of One
- 28,484
- 44,927
This is pretty much my approach when covering my ass and throwing someone under the bus. Just be diplomatic about it, but at the end of the day, you have to protect your interests above pretty much all else.
- 1
OU Ariakas
Diet Dr. Pepper Enjoyer
- 7,428
- 20,993
Yep, I would explain the whole situation and resolution including mitigation for the future. If they start asking specific names then I'd tell them exactly what they ask. No need to crucify the guy; but this is your job and he is not your friend. It was his fault and he should take the blame.
