From: Narbik Kocharians (narbikk@gmail.com)
Date: Mon Dec 15 2008 - 16:50:27 ARST
Andy,
Try explaining each technology back to yourself, Don't try to memorize
things, try to understand them. Once you understand a given protocol, you
will have an easier time to remember the hairs of each protocol.
Try to identify the features of each protocol and ask yourself how would i
implement that feature from CLIs perspective.
Try to configure, Verify and most important issue here is to test your
configuration. Testing the configuration is very important, try to see if
you can come up with a different way to test a given configuration, this
will help expand your knowledge and because you had to think hard to find
ways to test a given configuration, it will be easier to remember.
Write down your weak areas and hit them hard, do labs after labs after labs
and drill that given protocol until you laugh at it, go through the list one
at a time.
This works with me and i hope it helps you a little.
On Mon, Dec 15, 2008 at 8:30 AM, Ahmed Ibrahim <ahmadutj@gmail.com> wrote:
> Hi Andy,
> I have been having that problem too. You go thru the tech labs and
> come away feeling very confident but days later you can barely recall
> those 'interesting' details that made you think you were on the
> highway to IE city. Someone suggested taking notes that are short and
> straight to the point then later recording them to an mp3 player on a
> topic by topic basis. That way when you do not feel like picking up
> your notes for whatever reason, you can simply listen to Andy telling
> you about a technology as simply as Andy knows how.
> Yet to try it myself, but it sounds like a good idea.
>
> Ahmed.
>
>
> On 12/15/08, Andy Hogard <andyhogard@gmail.com> wrote:
> > Hi group,
> >
> > I have been working with the tech focused wbs, mainly the vol 1 of IEWB
> and
> > Advance Tech WB of Narbik. Now what I have observed is that, as time goes
> by
> > I tend to forget all the minute nitty gritty details of my experience of
> > labbing it all up. I do at times blog about it, but then that takes a lot
> of
> > time ya. Point being how are rest of you coping towards it.
> >
> > In the quest to solve the problem I went through numerous success stories
> > and came to conclude that the following points would serve as a
> > ready-reckoner for the days the come and will help me preserve those
> details
> > untill the lab,
> >
> > Technology feature:
> > Short description:
> > Command syntax:
> > Command location in the doc-cd:
> > For complex task a short eg, with dig and configs:
> >
> >
> > Any more suggestions eh?!
> >
> >
> > Btw, I am almost through with the 5 core technologies, but just wanna
> spend
> > some more time making sure that I know them inside out for untill the
> lab.
> >
> >
> >
> > Regards,
> > Andy.
> >
> > --
> > My Blog URL: http://ccieno.blogspot.com/
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
-- Narbik Kocharians CCSI#30832, CCIE# 12410 (R&S, SP, Security) www.MicronicsTraining.com www.Net-Workbooks.com Sr. Technical InstructorBlogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Thu Jan 01 2009 - 12:53:08 ARST