> can someone find a job with... pic programming knowledge only... or
> learning to program pic is not meant for job just for fu

"pic programming knowlege only" is not enough to get a job, IMHO.

First of all, "programming knowlege only" is pretty limitting.  In
general, it is more important to understand the problem you are solving
with your "program" than the programming itself.  This is why you can
find people with PHd's in computer science who are useless; unless you
happen to need something that exactly coincides with their thesis and
the environment they produced it in.  Since a PIC itself is so tiny and
pointless (unlike a desktop PC, for example), you have to know a fair
amount about the sort of things it can connect to.

Secondly, knowlege about a single particular architecture is limitting.
If you have a thorough knowlege of the PIC architecture(s) and
programming, you should have picked up enough about OTHER architectures
and languages to claim better than "PIC only."  If not, perhaps there is
something wrong with you.

There are probably some short term or "consulting" niches for someone
who doesn't do anything except PIC programming.  Probably NOT something
long term "that pays better than McDonalds" (over a long timeframe), or
with much of a "career growth path."

All those negatives aside, the "hands on hardware" knowlege of a typical
crop of "computer science BS's" is pretty abysmal, and the person who
built an 16C84 "LED blinker" will get the job offer over the otherwise
equal person who didn't, at least from me.

This is also, IMHO, what makes this such a good mailing list.  The scope
of discussion goes far enough beyond the PIC itself to make it almost
"well rounded"...

BillW