Ouma's Guide to getting ahead in IT

oumahexi

Free Range Witch
Local time
Today, 03:45
Joined
Aug 10, 2006
Messages
1,998
Top Tips to Get ahead in IT

If you are reading this article you are already aware that you are special. You are the person who becomes invisible in a crowd and could probably get by as criminal because few people will ever notice you enough to be able to describe you. This is why you are drawn to the world of computing. This is your chance to shine. New doors open for you and the key to these new doors is knowledge. In this industry you do not need to excel in your knowledge, a sound background will suffice. But in order to really shine, you need to follow some simple rules.

Rule 1 - Bullshit baffles brains

Whenever confronted with a colleague who appears to know as much as you do don’t be afraid to embellish your knowledge. Always talk up, and wherever possible, in circular movements. Talking in circles will make you sound like you know more than you do. But be careful, too many circles can make you sound like you are waffling.

Rule 2 – Knowledge is power

Never, under any circumstances, complete documentation. If you hand over full documentation so that another person can understand your work you will be as well to leave the job right now, the company has no reason to keep you as they now know everything you did. Always apply the 20% rule, that is, keep back 20% so that they need to ask for your assistance. This not only makes them look stupid but makes your look indispensable. Again, be careful not to take this too far, production of absolutely no documentation alerts your superiors to your game and they may feel that you are more of a liability than an asset.

Rule 3 – Use jargon

This works especially well with non technical staff. The use of jargon makes your sound as if you know what you are talking about and gives them greater confidence in you. When in meetings and discussions with other IT professionals make up some jargon of your own, this will make them think that you are really up to speed on the latest technology. Don’t worry, they won’t ask what you’re talking about because they are equally as insecure as you are and don’t want to look stupid. Once again, you need to be careful not to over do it.

Rule 4 – Keep it simple, make it look hard

Make everything you do look more difficult than it actually is. You can do this with the use of macros; embedded code and by using code supplied by others. Production of reams of unnecessary code look impressive when viewed by the untrained eye, and, you can employ Rule no 1 to justify its use. Couple this with Rule no 3 to add power to your reasoning. Try not to keep any code consistent. Consistency is easy to follow and will make you look average.
 
Good rules, with one exception. Rule 3.
The problem with being indispensable is you can't be fired but neither can you be promoted.
 
I used to call #3 "Technobabble". I had to work with a guy who was a master of it. I'm not sure where he came up with so much BS. It was really kind of funny and it worked, until a few of us called him out.
 
#1 Nobody knows as much as me here, I am the Access beast in their eyes since I apply my geek-speak whenever they ask questions so they just have to nod their heads acting like they know what I'm talking about and say "Ok do that, it sounds good."

#2 Good plan, I never intended to hold back for the sake of being indespensable but rather that taking down full and thorough documentation is a pain my ass. I leave things looking clear enough so that someone that knows what they're doing can come after me and understand with a bit of time - I don't intend to make a career for this - but anybody else is would have absolutely no idea.

#3 Even if I try to simplify a lot of times my boss seems to have the most unimaginative mind and never understands what I'm doing unless I've already completed it and show him. "Look, you click here it does this, you click here and it'll do this." Even then it takes him a while to understand it. Meanwhile the other employees at the meetings are entertained and feel good about themselves because they just about fully understand what's happening just not how, I keep that seemingly complicated.

#4 I always keep open a window full of the most untelligible code I can find while working on something really simple so I can browse this forum. Whenever anybody important stops by, I just open it when I hear the footsteps and put my hands in my hair while staring frustratingly at the screen. If they ever ask what's on the internet window I point out, "IT'S AN ACCESS FORUM AND NOBODY HAS THE ANSWER TO WHAT I'M TRYING TO DO!!!"... they'll usually leave me alone in peace for a good long time.
However, whenever you really look at my coding it's nice and consistent, I can't help having it any other way, I'm pretty damn OCD about keeping coding neat and consistent.

Good stuff though, Ouma, seems I already practiced a lot of those without realizing it with a bit of special tweaking for my office. I even got a hefty raise recently which came as quite a surprise. :cool:
 
#1 Nobody knows as much as me here, I am the Access beast in their eyes since I apply my geek-speak whenever they ask questions so they just have to nod their heads acting like they know what I'm talking about and say "Ok do that, it sounds good."

#2 Good plan, I never intended to hold back for the sake of being indespensable but rather that taking down full and thorough documentation is a pain my ass. I leave things looking clear enough so that someone that knows what they're doing can come after me and understand with a bit of time - I don't intend to make a career for this - but anybody else is would have absolutely no idea.

#3 Even if I try to simplify a lot of times my boss seems to have the most unimaginative mind and never understands what I'm doing unless I've already completed it and show him. "Look, you click here it does this, you click here and it'll do this." Even then it takes him a while to understand it. Meanwhile the other employees at the meetings are entertained and feel good about themselves because they just about fully understand what's happening just not how, I keep that seemingly complicated.

#4 I always keep open a window full of the most untelligible code I can find while working on something really simple so I can browse this forum. Whenever anybody important stops by, I just open it when I hear the footsteps and put my hands in my hair while staring frustratingly at the screen. If they ever ask what's on the internet window I point out, "IT'S AN ACCESS FORUM AND NOBODY HAS THE ANSWER TO WHAT I'M TRYING TO DO!!!"... they'll usually leave me alone in peace for a good long time.
However, whenever you really look at my coding it's nice and consistent, I can't help having it any other way, I'm pretty damn OCD about keeping coding neat and consistent.

Good stuff though, Ouma, seems I already practiced a lot of those without realizing it with a bit of special tweaking for my office. I even got a hefty raise recently which came as quite a surprise. :cool:

OK, I've set you up with an interview, it's just a formality really, you start in our office on Monday, your CV fits the bill. Can you make coffee? More to the point, can you drink coffee? Can you fit ten tea breaks into a morning? This is crucial, they will ask at the interview, the answer has to be "only ten?".
 
Just keep some assembly language code up on the screen. Preferably, some code with little or no comments. Guaranteed to dazzle, dizzy, or deceive those prying eyes.

My own favorite is VAX Assembly Language, even though our site no longer has any of its VAXen on the grounds. Alpha Assembly is just as good, though.
 
Rule #6 ALWAYS DELIVER 100% :)
10% on Monday
20% on Tuesday
50% on Wednesday
20% on Thursday
10% on Friday



Question: What happened to Rule #5?
Answer: I guess you need to have your email account security upgraded because it was forwarded to all the authorized recepients.
Oh but it did have the BLOG-guard turned on so if you have a blog, facebook or similar open on your desktop it will not be accepted because of the security breach last Tuesday. I'm sure you got that email broadcast...
;)
 
I am working hard trying not to disappear into cynicism but have to admit its not easy.
 
You can also convince the business/customer that they don't really know what they want and that they should follow YOUR advice!!

I know a lot of techies who earn their vittles with this technique.
 
Never hold back on teh Documentation

User the Access documenter

000's of pages full of the most detailed information that obviously removes any comments about the lack of documentation.

Have you tried reading this stuff ?????? !!!!!!!!!!!!!!!

Asleep in seconds

but fulfils the Technobableand documentation requirements in a single hit

L

L
 
As promised,
Rule No 5 - Never admit to anything

When it hits the fan, don't admit that any of it was your fault! There is always someone else to blame. For added support here, you might want to turn to sabbotage, when a collegue is not around, make slight changes to their code, it makes them look incompetent and you can step in and "see where they went wrong" in an instant. Now how good do you look? Next time you make a mistake the stage is set, all eyes are on the incompetent...
 

Users who are viewing this thread

Back
Top Bottom