Re: certification

[paw@northstar.dartmouth.edu]

Stephen Potter says:

	I guess the main point that I (and a few others) are trying to make is to
	keep the number of available badges down to a reasonable level.  Keep it
	down to skills that are particularly needed for SAs (almost mandatory).

Even if I agreed, at the moment I'll take any Merit Badge that someone
presented.  If we dither until we create the perfect set, we're right back
where we started.

	My particular "tirade" was because of the example job posting which got
	quite specific as to the badges wanted, including badges for PGP and SSH.
	All the most SAs are ever going to need to know about either of those is
	how to install it (read the INSTALL, it is pretty simple) and how to use
	it (again, read the README).  There is no reason for a merit badge of this
	kind, and I'd hate to see someone not be able to get a job because of not
	having a merit badge for such skills.
	
But if that's what that job was about, and the employer *needed* those
skills, then what's the problem?  You're saying we _shouldn't_ make it
straightforward to learn something because then people might want us to
know it?  There are plenty of jobs out there - if you're not into PGP or
SSH (and I don't think it's quite as simple as you make it out to be, or at
least not for everyone), then don't apply for jobs that require those
skills.  OTOH, the advantage to all is that by saying "PGP merit badge
required (or desireable)" _everyone_ knows what to expect.

I've had PGP on my machines for years, but never have integrated it into my
life.  Something that would make me do that, and walk me through it would
be quite valuable.  And, I'd've learned something in the end.

Pat Wilson
paw@dartmouth.edu