Discussion on:

10 dumb things IT pros do that can mess up their networks

Are you guilty of any of the infractions on this list? Do you agree or disagree that they're significant? What items would you add?

Ah ... but let us not forget that it should really be 'THE network', as opposed to 'my/our network'. For some reason many IT folks get very proprietorial about these things, and act like they really do 'own' them. Not so. Who paid for said network ? Not them, that is certain. So actually it's just another company asset at it's heart, albeit important, and we are simply paid to run and maintain it.

As the article suggests that is on ONLY reason you have a job to begin with, because of all those annoying 'users' that sadly you have to let play on 'your' network and break things. Think of it like driving a city bus, because big clever heads or not it's not so very different. "How dare you !" I hear the arrogant youngsters cry ... "I'm qualified, I went to college, I've got certs, I'm clever and ambitious" etc etc bleat bleat bleat ... well:

A: It's not your bus !
B: No passengers = NO JOB.

So yes, be nice to everyone, help as much as possible but don't make exceptions, unless it's a small setup, and you are dealing with the person that actually paid for the equipment and pays you ! Can't do much them except warn them !

Ah, what a life we lead ... oh and by the way OLE88, I don't do this 'because it's hard' ... it's because it's what I know, it's indoors and it pays well, or better than many things anyway. Please don't presume everyone thinks like you and sya 'we' ... in my, and I'm sure many other cases it's just a job I'm very good at, especially as an old lag with 20 yrs in. You'll see.

Muchas Rgds

TheMerchant

So you think that just because some corporate exec open the purse strings and bought some equipment they own the network. I don't think so. I built my network, I maintain my network, I put my heart, soul, blood sweat and tears into my network. I may let the users do their work on it but it is definitely MINE!

Yours ? Really ? Ha.

So, if you are fired, or the company is taken over, or whatever, I assume you will be taking 'your' network away with you then ?? What if you die in an accident ? Will they switch it all off as a mark of respect and start again ?

Doubtful. It's not 'yours' any more than it's your building ... your desk, your light fittings, your HVAC ... the list is endless.

Rgds

TheMerchant(of doom)

I'm not saying it is not your responsibility, because clearly it is.

For now at least I mean ... but nothing is forever. I imagine you are too young in years to have learnt that the hard way, unluckily for you. Maybe you will be lucky and never will have to, in which case more power to you sir ...

Let me first say that my original post was a bit tounge-in-cheek. However, seeing that you have set yourself up as the all knowing wise oracle I will fill you in a little.

I have been around working in this field since 5 1/4" floppies were brand new. I have been in and out a few shops at MY choosing.

The fact is I think that when you think of something as your own you take a pride of ownership approach to taking care of it. Of course a lot of younger people have no such work ethic and only care about "what's in it for me". You (the colective you, not you personally) would think that as long as these boards have been around that people would learn they never KNOW who they are "talking" to and not set themselves up as a know-it-all.

May have you beat in the age department.

I remember 8" floppy disks.

And used both punch tape and punch cards for program entry.

However, I'm NOT old enough to remember using a punch card predecessor for programming water-driven looms.

Let me first say that my original post was a bit tounge-in-cheek.

** I knew that **

However, seeing that you have set yourself up as the all knowing wise oracle I will fill you in a little.

** Just pot stirring, seeing what turns up **

I have been around working in this field since 5 1/4" floppies were brand new. I have been in and out a few shops at MY choosing.

** Likewise **

The fact is I think that when you think of something as your own you take a pride of ownership approach to taking care of it.

** I agree totally **

Of course a lot of younger people have no such work ethic and only care about "what's in it for me". You (the colective you, not you personally) would think that as long as these boards have been around that people would learn they never KNOW who they are "talking" to and not set themselves up as a know-it-all.

** You'd hope so. **

Me ? I know nothing really, other than what I've seen or experienced. So it's all opinion, not facts. It to me seems though that reality, as I interpret it, like the Gorgon, is not to be looked in the face by most. I, with much help of course, run a big 6200 node LAN. But none of it could ever be considered mine, in my view at least. However, I do freely admit there are flaws in my argument. By my reasoning an artist cannot 'own' their creation if they didn't make the paint, so I accept the logical inconsistency. I'm just entertaining myself, 'tis all.

TheMerchant

IT professionals refuse to know the old and true parable: ?The instant an employee feels indispensable, someone above is filling out his pink-slip.? I have a moron who thinks that he owns the network, and his pink-slip is filled out. Just a signature, and the fool will own not even a pencil.

The first network engineer I worked with, who taught me a lot, always referred to "THE Network" or "The Company Intranet" and never "MY Network" unless he was referring to the network he paid for and setup in his own home. I just wish someone would fill out pink slips on those individuals who try to hide things in an attempt to build "job security." They can make your job very difficult at times.

I knew of a company in Bracknell that got rid of thier network person who had been with the company from day 1(large company using extreme kit) he was on ?27000 at the time, so he ended up at the company next door on ?36000 (going rate)

The first company then decided to rollput VOIP having never upgraded the firmware or paid support (this was a 600 seat rollout) it all went pete tong (in the 11 years the tech had been there this network had never been down) cutting to the point this was Friday and it all had to be working by Monday morning so the IT Director went to phoned the tech and asked it he would help out

He said he would for his job back at ?60000 a year for the next 10 years in writting (he was 55 at the time) and they paid it and hes still there as this amount didnt cover one days daytime in sales (The person who made the decision to get rid of hime was gone Monday PM)

Taking ownership and responsibility is fine. And you may be trying to make some point, but it is lost in you taking on the persona of the "power hungry" sys admins that many of us are way to familiar with.

In our shop we take ownership of the maintenance and issue resolution of our system. But we get paid. I may write a beautiful process and configure my firewall with elegance. And then the people that pay me to work or their hardware take what I gladly exchange for the money.

If this strong emotional connection that you are expressing in your post is legitimate, then you need to wakeup and get some professionalism.

I love working on networks, and enjoy using the expensive hardware that I get to use at work. But if they didn't pay me would I do it anyway? Absolutely not!

If you feel the network is you baby, you need to get a life.

It is nice to know there are those still around that are above me in the age ladder.

Ah, yes... 8" floppies - double sided by flipping them over, 8 level paper tape for backup of the boot load, and mounting 5Mb hard drive platters and when they crashed, they REALLY crashed!

I even remember 'finger-boning' in the boot sequence using the 16 switches on the front panel when the paper tape reader wouldn't read.

But, no, I don't remember vacuum tubes in computers

It was only 12 short years ago for me, but I remember working in a shop as a field service tech and learning how to IPL a DEC PDP machine, playing with paper tape, reel-to-reel mag tape machines and all sizes of floppies. Those were the days!

In addition to the attempt to make I.T. look stupid you ripped off ISO best practices. All best practices are subjective and on a case by case basis. Nothing in life is that easy or it would have been mandated and incorporated into I.T. equipment long ago and you would simply have no choice but to do it to use it.

As for the comments by MerchantBanker your whining about the I.T. Gods. Now days they make pills that will take care of your problem. You could also get on your knees and beg forgiveness to the next I.T. God you see after all we not only own the Network we created the Network.

Dear Sir,
If your must chide me so at least learn to punctuate and spell, that I may better be scolded ...

Well I can see you wont be my teacher. Every time one of you clowns get handed their lunch you worthless arrogant snobs always go to spelling, punctuation and grammar nonsense. With the rarest of exception Every time you clowns make spelling, punctuation and grammar mistakes. Your statement starts with "If your must chide me" which you then go into the formentioned spelling, punctuation and grammar nonsense.

I consider your comment a declaration of defeat and I accept it as such. Now go away dork.

Oh dearie me. Calm down man, you'll pop a vein !

Where would you like me to go by the way ? Somewhere nice ? If you like I can try and pick up a sense of humour for you whilst I'm there ? You've got the space available for one.

Rgds:
TheWorthlessArrogantClownSnobDork (Jnr)

PS: Sigh. What sort of feeble insult is that ?

Well So far from this thread I have learnt a few things

Firstly being around since floppies were really floppy does not preclude one from immaturity, naievity or all-round pathetic-ness (sic).

Secondly Network admins have too much time on their hands and not enough work/stress allowing them to peruse equally worthless boards/threads searching for that elusive punter to flame.

Honestly GET A LIFE.

I have never seen such a pathetic excuse for a thread degenerate into such an entaglement of stupidity

I will leave it to the preceeding posters to work out who this is referring to to those that dont care who could blame you

PEACE...!

I say if the IT techs have time to discuss, then its one of two things. One, they know their stuff and their networks don't need the attention. Or two they just have too much time on their hands and don't know what they are talking about. Let them vent on each other because it really is a good read. I really like what MerchantBanker has to say. I myself am only a student, and am new to the field. But leave them alone and let them discuss, its healthy.

Just reading this makes me think of some of the things on the list that I do my best to do proactively. However, there are some that I either don't think about or have not visited in a while. Of course, the job of an IT professional is not easy (or we wouldn't be doing it). Between users, problems, management and trying to keep as current as possible on technology, it gets difficult to keep up with being proactive and keep things like this up to date.

The one I run into more from others is #10 though. Many people I work with refuse to share information, documentation and/or resources because they feel that it makes for better job security. They will never listen to reason but changes are coming from the top that will hopefully put an end to this. I would have to say that my biggest pitfall is #8, trying to please everyone just so you don't step on any tails. I don't go as far as the example, but there are people here that you just can't reason with even when you show them the policies (in some cases that they signed into existence).

I am going to print this off and present it to my team so we can ensure we do our best to maintain uptime and be more proactive instead of reactive.

Yes we all try and keep the list in our heads but I for one am posting it in my server room.
Especially since I just started in this positon as Systems Administrator and I am still trying to figure out exactly what I have inherited and and what condition it's in!

If it absolutely, positively can't be fixed immediately; document the problem, the temporary fix/work-around (you do have one, right?), the delayed 'correct' solution, and why it's being delayed, and contingency plans for if it fails.

That way when the house of cards comes tumbling down, and it will, you'll have an idea of how to pick up the peices, and some protection from the forces that crammed you into the untenetable position in the first place.

I'm beginning to think that no one should ever be allowed to be a manager until they've had a full college semester or two of a Disaster Preparedness for Business course.

making that one happen. There are a few too many out there that would flunk it and they don't want to look stupid when it happens. Of course a number of them look stupid just opening their mouths.