mspitzer at gmail.com
Wed Sep 21 17:47:55 EDT 2005
On 9/12/05, dlavigne6 at sympatico.ca <dlavigne6 at sympatico.ca> wrote:
> What is your view on recertification?
needed unless we go the cissp route and handle continuing education
credits in addition to recertification
> The downside: inconvenient, can be seen as a "money grab"
Anything that costs money will be seen as a money grab, by some at least.
> The upside: required for NCCA accreditation which is one way to give BSD certification value--however, NCCA allows us to define the recertification time period and criteria
> If there is to be a recertification:
> 1. should it be by time period, and which period? every 3 years? every 5 years?
4-5 years seems to be a fair compromise
> 2. should it be by version number? e.g. if certification was in FreeBSD, should it be when a new release tree is released? e.g. someone certified on FreeBSD 6.x would need to recertify within (e.g. 6 months) of FreeBSD 7.x going stable
I think this is more of a certification rather rthen a recertification
question, what the Cert does the recert will follow
> 3. if someone is an "associate" and writes the "professional" sometime before the recert period is due, should the recert clock start ticking over again?
yes it should, you just took a harder test on the same material so
should be set to when the professional test is to be recertified.
Special upgrade tests, that do not cover the full breadth of the
subject at hand, should allow you to claim the new level but not reset
your clock. And I am not even sure this is a good idea, upgrade tests
"We trained very hard, but it seemed that every time we were beginning to
form into teams we would be reorganized. I was to learn later in life that
we tend to meet any new situation by reorganizing, and a wonderful method it
can be for creating the illusion of progress, while producing confusion,
inefficiency and demoralization."
-Gaius Petronius, 1st Century AD
More information about the BSDCert