> I think thery were lookign for, could i even *give* the
> specs. I mean, most
> geeks know some of that, even if they aren't hardware
> geeks. Soem have very
> deginite opinions about why they got thus and such a part
> as opposed to
> another... they were looking afor someone who knew there
> was a difference
> in other words. Which is not a bad basis for hiring an
> entry level tech.
> That was a big company too, but probably the the ONLY
> intelligent
> discussion I had with management there :)
> Dana
> S. Isaac Dealey writes:
>> Let me guess -- they didn't want to know the specs (ram,
>> cpu, etc)...
>> :)
>>
>> > The best interview question I ever had asked of me (for
>> > tech support) -
>> > "Describe your computer to me."
>>
>> > Dana
>>
>> > Dan Phillips \(CFXHosting.com\) writes:
>>
>> >> To me, I could care less if they have a cert. It's all
>> >> about experience.
>> >> That's why doctors have to work in hospitals a few
>> >> years
>> >> before they can
>> >> graduate and even then, its more work in the field
>> >> before
>> >> they are given
>> >> more advancement.
>> >>
>> >> One problem I see are these "technical schools" that
>> >> promise to have you
>> >> in and out in 6 weeks with an MSCE, MCP, CCNA, A+,
>> >> etc.
>> >> They just have
>> >> you memorize answers to the tests and send you on your
>> >> way. What really
>> >> kills me is that they also tell you you will be making
>> >> 70k a year as
>> >> soon as you graduate and get your first job. That may
>> >> be
>> >> the case with
>> >> some people but I don't think the companies hiring
>> >> them
>> >> know much
>> >> either.
>> >>
>> >> I started at the bottom and worked my way up. I was
>> >> lucky
>> >> to find some
>> >> small family owned consulting service that was willing
>> >> to
>> >> let me learn
>> >> and teach me as I worked there. I made less then 20k a
>> >> year but I was
>> >> getting real world experience with network, repair,
>> >> programming, web
>> >> design, concepts, you name it.
>> >>
>> >> I've worked side by wide with MSCEs who just learned
>> >> about computers 12
>> >> months before and it shows. They can only troubleshoot
>> >> what they know
>> >> and not rule out anything outside their scope of
>> >> knowledge. I've also
>> >> worked with people who started programming on an Apple
>> >> II
>> >> when they were
>> >> 6 years old and they are a wealth of knowledge.
>> >>
>> >> Some kind of mentor program may work. If I was hiring
>> >> anyone, I would
>> >> really take a look at what they have done with
>> >> technology
>> >> as far as a
>> >> hobby and in previous employment.
>> >>
>> >> IMHO
>> >>
>> >> -----Original Message-----
>> >> From: Dana Tierney [mailto:[EMAIL PROTECTED]
>> >> Sent: Wednesday, October 01, 2003 12:10 PM
>> >> To: CF-Community
>> >> Subject: Re: Re:CF Salary Range
>> >>
>> >>
>> >> > We need to get out of the certwhore IT mentality,
>> >> > and
>> >> > need to realize
>> >> that practical experience under the guidance of
>> >> mentors
>> >> is a required
>> >> component in create quality IT people.
>> >>
>> >> Perhaps an apprenticeship program. Or certification
>> >> that
>> >> requires
>> >> hands-on
>> >> knowledge. I've talked to my share of ignorant MCSEs.
>> >> But
>> >> perhaps the
>> >> problem is in THAT certification rather than the whole
>> >> certification
>> >> concept.
>> >>
>> >> Dana
>> >> _____
>> >>
>> >> [Todays
>>
>> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> > ~~~
>>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
