[gameprogrammer] Re: Fire on the first day?

Let me get this straight. You hired the guy without checking any facts about
his claims? Then on the first day you ask for something that's a typical
interview question, and you expect something that belongs in a portfolio?

Maybe it's just me but you're way too late, you'll have to try him out now.
Let him prove himself, by showing you what he meant.

/JP

-----Original Message-----
From: gameprogrammer-bounce@xxxxxxxxxxxxx
[mailto:gameprogrammer-bounce@xxxxxxxxxxxxx] On Behalf Of Paul Smith
Sent: den 24 mars 2007 00:09
To: gameprogrammer@xxxxxxxxxxxxx
Subject: [gameprogrammer] Re: Fire on the first day?

My 2 cents here:

Reviewing resume, references, portfolio etc is pointless here.  What
you want is a demonstrable prototype of a solution you've jointly
designed which you can get real, up to date information from.

If he's not up to the task of *implementing* a simple prototype, then
you have issues.  If you see a simple prototype in a short time scale
and you're impressed, then you've got the right guy.

On 3/23/07, Chris Nystrom <cnystrom@xxxxxxxxx> wrote:
> On 3/23/07, Kevin Jenkins <gameprogrammer@xxxxxxxxxx> wrote:
> > I hired a graphics programmer for my 3D space game.  He sounded smart
> > in the interview and sounded like he had a good background.  His first
> > assignment was to develop an explosion system for a giant carrier.
> >
> > When pressed on how he would do this, he said he would place explosion
> > billboards randomly inside the bounding rectangle of the carrier.
> > When asked why this would work, he said it would work because my test
> > carrier was a giant (hollow) rectangle.
> >
> > For those that don't know it, the bounding rectangle of an object is
> > the rectangle that encloses the maximum extents of the object, and
> > unless the object really is a rectangle will have space outside of the
> > object too.
> >
> > My immediate reaction, and maybe I'm wrong, was that his answer was so
> > obviously wrong no graphics programmer could ever give it.  Even
> > non-programmers should know better.  Did he actually think our final
> > art was going to be flying rectangles?  Or did just not think things
> > through?  Either way, I should just fire him immediately.
> >
> > On the other hand, I don't want to be an ogre that fires someone just
> > for asking a question. I always hated jobs where I had to spend hours
> > figuring stuff out because someone couldn't spare 5 minutes to answer
> > something.
> >
> > Firing now will cost $200 and the time I spent interviewing.  Waiting
> > will cost me $1000 and that time, but has a chance that he will work
> > out in the end.
> >
> > What should I do?
>
> It is hard to find good help these days.
>
> In the future you might ask more questions in the interview relatated
> to the first assignment, so you can have better confidence that at
> least that first assignment can be completed.
>
> Cost already spent is water under the bridge. Think of it as managment
> training expenses.
>
> As for now, you need to know as soon as possible if he is the right
> guy for you, or not. Why not talk to him some more? Can you review his
> resume, references, and portfolio closer?
>
> Chris
>
> --
> E-Mail: Chris Nystrom <cnystrom@xxxxxxxxx>
> Saving the world from web programming.
> http://www.newio.org/ - AIM: nystromchris
>
> ---------------------
> To unsubscribe go to http://gameprogrammer.com/mailinglist.html
>
>
>


-- 
Paul Smith
Computer programmer

paul@xxxxxxxxxxxxxxxxxx

---------------------
To unsubscribe go to http://gameprogrammer.com/mailinglist.html

---------------------
To unsubscribe go to http://gameprogrammer.com/mailinglist.html

Other related posts: