I never say that line. I read an article that said it's the worst thing one can say on the job. I do a lot of work. What gets me pissed is when I complete a bunch of stuff, and Mr Dementia asks me what's going on. I did this, this, this, and this. Good, what are you working on now? Like everything I just completed doesn't mean crap. That's the cycle I'm talking about."Not my job" was the defacto response when anything hard came up.
I never say that line. I read an article that said it's the worst thing one can say on the job. I do a lot of work. What gets me pissed is when I complete a bunch of stuff, and Mr Dementia asks me what's going on. I did this, this, this, and this. Good, what are you working on now? Like everything I just completed doesn't mean crap. That's the cycle I'm talking about.
Now he's going to deal me some crap project I don't want to work on. Instead I'd rather work with the BAs. So I have to BS that I'm working on something else. All he cares about is what I'm working on now and how long will it take. I've completed another project that's going through QA, but I'll tell him I'm still working on it with the BA.
This. I'm no god at any of it (though I've worked with a few who are now mostly at Google), and having done telco network ops for 20+ years now (though technically I'm not really doing the day-to-day stuff now, more making sure things are in place for the Indians to flow-chart their way through), I've absolutely had to tip my hand at being all of those things to some degree or another. I've built servers, designed DBs, optimised them as needs changed, plugged into other people's ones, built web apps, portals, reports, and I can even make a pretty mean excel graph if it doesn't crash first and then link it into a powerpoint to explain to execs "why that thing".
It's really not that complicated if you have half a brain and can adapt, and if you want to be any good at any of them, you need to know how all the rest of it works anyway.
It's all interdependent.
You created a thread whining about DBAs, you fucking baby. Might want to take a look inward.
I love looking down on you whiny inept shitbags.you had to look up dba to even know what it meant. Move along
I never say that line. I read an article that said it's the worst thing one can say on the job. I do a lot of work. What gets me pissed is when I complete a bunch of stuff, and Mr Dementia asks me what's going on. I did this, this, this, and this. Good, what are you working on now? Like everything I just completed doesn't mean crap. That's the cycle I'm talking about.
Now he's going to deal me some crap project I don't want to work on. Instead I'd rather work with the BAs. So I have to BS that I'm working on something else. All he cares about is what I'm working on now and how long will it take. I've completed another project that's going through QA, but I'll tell him I'm still working on it with the BA.
Hey does glytch make money? He hasn't said anything about it and we are all on the edge of our seats wondering about it.
Bring it. I dont care.Hey Falhawk, I've never mocked you like everyone else does. Let's leave it at that shall we?
I love looking down on you whiny inept shitbags.
Your problem is not with DBAs, but a stupid, affirmative-action woman. You'd have to have a brain to get that, but I get why it's a struggle.
If you had balls, you'd let it fail (or ensure it) and appropriately redirect the outrage. Corporate life.
Two co-workers have said that when he calls us into his office, ask him, "What are you working on?"
Consultant to VP at two different multi billion dollar companies but pretty much the same idea.
gr8 wyte trash cuckthred juggernaught ya fukn pussyass disgr8c 2 ya own race frenz n famly dat betta off ded 2 smdh lol
So you advise the VP on which coffee he should have to match with his socks?
sweet job bro