On 8/22/2010 12:00 PM, [email protected] wrote: > Valid points by all that suggested letting the network guy be the > network guy and just focus on managing. > > One counter-point I offer is that if no one else in the group knows > enough about networking to cover for that network person at a base level > (basic troubleshooting and device configuration), then at least one > other staff member needs to learn more for breadth of coverage. That > doesn't have to be Damion as he is the manager, but he might assign the > task to someone else in the group.
I don't know that I'd consider this a counter point to the original statements. It's an excellent idea to have one on or more of the current systems people learn at least the basics of the networking tasks, so that they can step in when needed. It's just the wrong idea for someone who is in charge of the group to be the one to do it. I recognize that often, a person who is the titular head of a group is also one of the working members, but a choice needs to be made as to whose time should be spend learning the new tasks, and I'd think that it was not a good use of the time of someone who should be managing to take hours and ergs of energy from those tasks in trying to learn a new skill. All those suggestions as to how to pick up these skills are very good ones, but they should be applied to one or more of the subordinates on the team. -- Little known fact about Middle Earth: The Hobbits had a very sophisticated computer network! It was a Tolkien Ring. _______________________________________________ Discuss mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
