I showed those images to a colleague (I work as an analyst on the software side, he's hardware) and he pointed out that you can easily trace where the wires go on those as there are empty ports, no one's added a few extra 8 or 10 port switches to the top of the patch bay and there appears to be some form of colour coding going on rather than everything being just grey. He dreams of a comms rack that was that tidy
Hey, that's bad but nowhere near as bad as I've seen. Did you move this hardware to a bunker datacentre or were you removing it from one? I pity the guy who both thinks that's in any way acceptable and who has to work with worse. I really don't get it with comms cabinets. There are neat, tidy, "I have a shred of pride in my work" ways of doing things and there are "plug it in and make sure it works, I don't care what it looks like" ways of doing things.
Removing from both those pics are from Ash not got any from Newbury. Ash still has a beautiful radar control room from 2nd world war Newbury has worst access ever to get kit in and out but is a wonderfull view over the common from the flight control tower
Agreed. My old job seemed to go with the along as it's plugged in it's fine. Part of the reason I left. Couldn't stand messy environments. My current job brings a tear to my eye every-time I walk into one of the on-site data centers. Cables are beautifully tidy. Each patch panel and fly lead is labeled and to which switch - module - port number. Ahhhh
At our place we have cabinets where the doors won't close due to the mess of cables. My record is 13 minutes to trace a 2m cable from patch panel to switch. I don't even work on the Network team (Though I have a degree in it...)
That's the sort of unacceptable thing I can't put up with. They should pull the whole lot and redo it. You can trace a patch in any of my installations in less than a minute, usually much less because you just look at my port map/diagram which is always beside the cabinet. My installs are more like what Votick described... Everything labelled and tidy.
You know, I've tried to explain to my boss that cable management pays for itself in time saved day-to-day, but he still grumbles that I'm wasting time if I start tidying up our spaghetti-like desk (and impatiently cuts my cable ties a day later). Because God forbid we actually manage to find stuff when we need it.
unplug his cable in the lot, and then spend half a day trying to work out which one it is because of the mess?
Unplug his cable and make him find it in the mess [which you've accidentally on purpose made worse...]
As I've mentioned in another thread, our school computers are being replaced and the network upgraded this week - it's a fairly large job, so there's a team of four "engineers" here from CAPITA performing the work. The lead site engineer is a nice chap with his head screwed on. An actual qualified network engineer, he's intelligent, logical, sensible, very obliging and generally great at what he does. A couple of the other guys are fine too, good at what they do but not much else. Not really engineers. The last guy has been late for work all week, asking stupid questions like "is that the new server" (whilst pointing at the only thing that could be the new server) and "are these getting 64 bit images?" (when the laptops he's pointing at are too old and slow to run an x64 OS) etc etc. The final straw though, that told me he knows less about computers than a 6th year student, was when he had to ask me what the dual screen setup in the Principal's and IT Manager's offices were for. He literally couldn't get his head around the point in it. "Oh yeah one of my mates who works in place xyz has two screens in his office. He says it's OK, you get used to it, but if you mess something up it's a balls to fix your mistake". At this point my mind was fairly well blown, but wait, there's more! I'd pulled the graphics cards out of both old machines before they were taken out of the offices, and when installing them in the new machines before they were set up, I was asked "what's that? What does it do?". That's right, an "IT engineer" who didn't know what a graphics card was or what it did. He never shuts up either, always talking a load of crap about jobs he's been on, schools he's been in, teachers he's dealt with etc. As if I care about any of that Krikkits quote in my sig is 100% gospel. The country is full of cowboys. I don't know where they found this guy!
I think I should move to N. Ireland and start job seeking. It sounds like I'd be running the country's IT infrastructure in a week
Haha, you're not far wrong! Something tells me this particular 'engineer' bluffed his way info his job.
Yes, so much! Funny you should post that - in the video he refers to the base unit as the "hard drive" and Jen agrees. Acceptable names for the "bit that goes on the floor" (or on the desk, as with desktop units like our new Optiplex 3010's, one of which I'm posting from now, or like custom built tower cases which gamers and modders love to show off! ) Base unit Tower Main unit PC Computer Station Unacceptable names: CPU Hard Drive My new (least) favourite "engineer" called it a CPU yesterday
yeah, I have a lot of customer refer to their towers as hard drives. Some even say, "you know, what's it called, the hard drive" - but these are all just users and not IT guys. I had to explain at length the other day to a technical IT manager how to reboot a server from the command line... I took some pictures the other day I keep meaning to stick in here, but I am about to go on site now so I don't have the time, hopefully I will remember tonight. You missed an acceptable term: Box - I am bad for referring to most things in IT as boxes Servers, workstations etc.
