🚀 go-pugleaf

Kind of one of those how long does a ball a string need to be to reach from
New York to LA.

Answer: As long as it needs to be....

Being a seasoned developer, it took me 6 months. And after that another 6
before I started to "internalized" Access. What I mean by internalized, is
that I could "think" in Access, and come up with solutions that are *really*
appropriate for Access. At first one learns the syntax of the language etc.
After that, one learns what works well, and what to avoid. It is this art
and learning that allows one to really fly with Access. In other words, I
can learn the syntax of all the commands...but that is not enough compared
to "what approach works". After a few stumbles, and looking at where/why
some of my projects dragged on, I finally began to get a handle on
ms-access.

However, the general break down of skill levels for a *GOOD* developer is as
follows:

   Stage 1 Innocent (never heard of the product)

   Stage 2 Aware (Has read an article about X)

   Stage 3 Apprentice (has attended a three-day seminar)

   Stage 4 Practitioner (ready to use X on a real project)

   Stage 5 Journeyman (uses X naturally and automatically in his job)

   Stage 6 Master (has internalized X, knows when to break the rules)


One should NEVER attempt a project with a team consisting with Stage 3 or
lower people. This is a sure fire formula for failure. The team can consist
of 4's, but should have access to 5, or 6 type developers.

--
Albert D. Kallal
Edmonton, Alberta Canada
kallal@msn.com