posted on Jul, 20 2004 @ 01:22 PM
Sorry to hear you got fired; hopefully you'll have good luck finding good (hopefully better) work soon.
Just general words of advice:
A) In any office environment office politics are always more important than you think they actually are, and this goes double for people who are
handling more technical matters (as opposed to more customer interaction / meeting sort of things). Trust me, I'm as geeky and antisocial as they
come, but I've learned that failing to pay attention to the office politics and personalities at your place of work is gonna always wind up hurting
you in the long run.
B) It sounds like the "other guy" -- the security engineer -- didn't really know his stuff, i.e., he's probably incompetent. Now, people can
handle their own incompetence in a lot of different ways, including:
i) ignoring it / being ignorant
ii) recognizing it and working overtime to learn the stuff, get competent, etc.,
iii) same as ii), but acknowledging it to superiors, etc.,
iv) trying to hide the evidence and keep superiors from knowing, etc.,
and it sounds like the security engineer was probably aware he didn't really know much about current security practices, and was afraid his bosses
were going to find out.
Here's where you come in: in a perfect world, when you're like
"yo, your info's out of date by 10 years"
he'd be like
"dude, thanks man, I should totally start getting back up to speed. thanks dude"
but instead he was probably thinking
"uh oh, this guy knows more than I do, he'll probably be after my job soon, and then I'll get passed up for promotion"
and then he thought
"uhm, he said he knew some hackers...maybe I can convince OSI to investigate him and get him fired"
and then yeah, he went and did that.
As a lot of people here have already said, once some OSI guy sees you're visiting here a lot -- with a name of abovetopsecret.com -- that's
suspicious enough to freak the guy out, and even if you're being totally harmless it shows bad judgment to visit on work hours, so that's probably
enough to get you fired.
Worse, though, is that if the OSI guy finds all this stuff about you, and you're like,
"man, I just go for fun, I'm not a hacker, and I keep my mouth shut about what I know"
and he's like
"dude, I see, oh well, sorry to bother you"
if you turn out to BE a hacker -- or even if the network gets hacked -- now the OSI guy's boss is gonna be like
"yo OSI man, you let this HACKER keep working here, nice move, I'm demoting you"
(never mind that you're not a hacker)
so now the OSI guy has to cover his own behind and the safest thing for him to do is just to fire you.
So, here you are: fired, and without a chance to explain yourself. I wouldn't read anything into it more than bad office politics and the CYA (cover
your "behind") principle at work.
So my $0.02 is: if you're gonna stay in a technical field, learn to pay more attention to office politics and learn to anticipate how people are
going to react to things; any good hacker will tell you social engineering >= technical skills, and the same goes double in the real world.