Methodology

From: Joseph Rinehart (jjrinehart@hotmail.com)
Date: Mon Sep 16 2002 - 18:33:44 GMT-3


New Thread, dealing with strategy.

Personally I feel that I will probably be ok in terms of the technology and
overall configuration. I am not claiming to be prepared yet, but I am
saying I think that part will end up adequate. My question is about
strategy, because even in my practice sessions and hands on stuff I find its
stupid little stuff that tends to kill my effectiveness (mistyped commands,
forgetting to put in something I even had written out, etc.)

My approach is usually to read requirements, read them again, and then start
by drawing a diagram, and including addressing and other pertinent
information. Next I will write out a configuration and go over it several
times, and only then start coding the routers.

What do you feel is a reproducible strategy to the lab? What methodology
helps minimize mistakes and confusion and helps you avoid throwing away
points outr of sheer stuidity?

Joe



This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:53 GMT-3