A Day In the Life of a Network
Architect
By an Evil Network Architect

Here is a comprehensive description of the
average day of a networker…well, you know.
10:30 AM - 10:35 AM Wake up kiss twins girlfriends good morning.
10:35 AM - 10:45 AM Shower, Shave.
10:45 AM - 11:00 AM Eat balanced breakfast (coffee with coffee, and a
side of coffee over coffee).
11:00 AM - 11:05 AM Review emails for critical items.
11:05 AM - 11:15 AM Forward them to personal assistant.
11:15 AM - 11:15 AM Make difficult policy decision. Do I drive the
Jaguar XJS V12 or the Porsche Boxter S?
11:15 AM - 11:30 AM Drive to work
11:35 AM Accidentally spill coffee on clothes. Have nasty disposition.
11:40 AM - 12:00 AM Write global policies for implementation by MIS
Directors, and network admins in offices around world. Laugh
maniacally!
12:00 PM - 1:00 PM Lunch meeting at sushi bar.
1:00 PM - 2:30 PM Arrive home for not so quickie
2:30 PM - 2:30 PM Arrive back at work.
2:30 PM - 3:30 PM Meeting with CIO, local MIS Director and random
losers
3:30 PM - 3:45 PM Meet privately with CIO, joke about losers at
previous meeting, make fun of personal flaws and or speech
impediments.
3:45 PM - 3:50 PM Agree on overall strategy.
3:50 PM - 4:30 PM Write strategy and project plan.
4:30 PM - 6:00 PM Gather all information necessary and review it.
Re-attain guru status on all aspects of the project 6:00 PM - 7:00 PM
Take twins to go see newest blockbuster movie
7:05 Find dark quiet corner in back of theatre
7:20 PM - 9:00 PM --- Censored ----
9:00 PM Casually wonder what movie was about
9:00 PM - 10:00 PM Dinner at quiet restaurant
10:00 PM - Difficult decision increase my frag count on Counter-Strike
or Twins?
1:00 AM Sleep
2:17 AM Phone Rings with mission Critical Problem.
2:17 AM - 2:30 AM Ask brief concise questions as to the problem
symptoms, request additional information be looked up by available
techs. Keep close eye on time, minute by minute re-evaluating fastest
way to bring systems back up to operational and functional status.
2:30 AM - 3:30 AM Write minute by minute report of downtime, the
measures taken and why. Include procedures for preventing the issue
from occurring again. Prepare to meet with CIO, and hand him all
information needed for meeting with CEO. Send comments to:
|
|