|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary
[1,407]
Women 4 times more likely than men to cough up personal info
[589]
Japan's 10 funniest tech-related commercials [Videos]
[407]
Throwing away a promo CD is "unauthorized distribution"?
[1,265]
Adults too quick to dismiss educational video games
[682]
Attack of the iPhone clones [Slideshow]
[578]
10 things IT needs to know about AJAX
[1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow]
[409]
|
|
He's not doing the best thing for the city.
I have worked on several large networks in my career. I also put my heart and soul into the design and implementation. I spent many hours on my own working on config's and the network was my pride and joy.
However, I had detailed network diagrams of all sites, I kept them in large picture frames on my walls and when there was a change I noted it with a dry erase marker until I had a chance to update the drawing. I standardized all passwords and kept them in a safe place where someone knew where they were. I trained the people under me as best I could. Everything I did was with the thought that if something happened to me someone else could come in behind me and take my place.
The end result? When I moved on to another job, another engineer would be hired behind me. Most of the time they found something to criticize is a way to establish their value. Any new problems would be blamed on me because I was an easy skapegoat. My leaving was for the most part an uneventful and soon forgotten passage of time.
That is the mark of a true professional network engineer. Childs was a true amateur and a disgrace to his profession.