Re: Recommend a project.

Randy,

In a way you are right. An employer can look for ppl who know
how to write some applications but do not necessarily mean they
are good at it. From my perspective, the shortcut is to get someone
who know how to do development on the product at hand. Which is okay
but many at times it get pretty crazy when someone tends to write just
for the sake of the job. You are correct that if a person want to talk
only about MP3 at the embedded level he would probably be hiding some
facts that he does not know about USB stuff at hand. Now comes in this
statement, we all start from somewhere don't we? Just b'cos the
interviewee does not know about USB does not necessarily mean he
wouldn't be able to learn about USB quickly. Of course his experience
in using other protocol would BE an advantage and possible determine
his capability in learning new protocols. To be frank my work
experience suggest that I am a business application programmer which
tends to lean on the back end. But does my capability ends there?

Off the job I have learnt more on MCU and did some work on it. There
are other low level stuff which I continuously kept on learning more
each passing year. Which I am starting to use more lately off the job.

So does it mean I am only constricted to only business apps? Btw, I
think it is crazy for a respective employer to just listen to my rants
but I need to show some evidence on my skills like a webpage which
perhaps describe the projects I work on. Which I believe you will
agree with the amount of work and effort you have done which your
webpage.

John

On 29 Sep 2006 10:32:57 -0700, "randyhyde@xxxxxxxxxxxxx"
<randyhyde@xxxxxxxxxxxxx> wrote:


Betov wrote:


Having written all the programs you've listed, and having them all on
resumes,

Too bad we never saw anything real.

He who refuses to see the truth...



and having interviewed perspective employees over the years,

Oh! My goat!!!

No, I never interviewed your goat. I have personally managed about 20
programmers over the years (mostly at small and medium sized
companies). The positions involved many different types of programmers,
though mostly in the embedded area.

The
*only* work that will impress most perspective employers is work that
is similar to what they're already doing.

Of course not. They will evidently be more impressed
by what they do not know, instead.

If I'm looking for a USB device driver programmer and you start telling
me about how you programmed an application to play MP3s, I'm not going
to be very impressed. I want to know what you've done in the area of
USB device drivers. In particular, if I'm working on a USB printer
device, I want to see example code that demonstrates that you
understand the USB class drivers for printers and how they interface
with the rest of the system. All your knowledge about MP3s may be well
and good, but it's totally useless information for the job at head.
Indeed, if you started rattling on about your MP3 application, I'm
pretty sure I'd take that as a sign that you're trying to hide your
lack of knowledge about USB device drivers. In an interview, you want
to be concise and to the point. You don't want to waste the
interviewer's time with a lot of peripheral knowledge that has nothing
to do with the job at hand.



If you want to work in
assembly language (exclusively, more or less), that pretty much means
writing BIOS or library routines for HLLs. I'd recommend the latter.

Recruiting for your absurd Library again, clown?

Not really. But libraries (for HLLs, not assembly language) is one of
the few areas you can still get employment as an assembly language
programmer. I realize that you wouldn't understand this, because no one
would hire you to write assembly code for them (so you don't have a
clue what people would want assembly language written for), but the
fact that you don't know something doesn't mean that the world at large
doesn't work that way.
Cheers,
Randy Hyde
.

Relevant Pages

  • Re: Programmers unpaid overtime.
    ... >> It is that white collar people know, in their heart, that their ... correction which is pretty much the entire basis for "programmer" ... > Let's just hope that some prospective employer of yours reads this stuff ... perhaps by the emplacement of anti-labor and anti-solidarity agents by ...
    (comp.programming)
  • Re: Bonuses, again.
    ... version of whatever programming language the employer wants me to use. ... They'd rather pay an enormous salary for someone who can start being ... expert Java programmer in May. ...
    (rec.arts.sf.fandom)
  • Re: future in software industry as a lisp programmer
    ... it is not a practical thing to be a programmer any more. ... as I've developed technology for computer-assisted ... learning disabilities such as dyslexia or trouble-remembering to ... employer who would look at some of the technology I already ...
    (comp.lang.lisp)
  • Re: VB.Net and Outlook
    ... You are using an ActiveX control to send mail. ... using Outlook functionality per se. ... I do not answer questions on behalf of my employer. ... >> programmer helping programmers. ...
    (microsoft.public.dotnet.languages.vb)