Forgot your password?
typodupeerror

Comment: Re:Can't Tell Them Apart (Score 1) 466

by DaWhilly (#46997729) Attached to: Ask Slashdot: Minimum Programming Competence In Order To Get a Job?

We started out having the test sent before interviews and it worked for about 3 months. Then we told HR to start sending an updated test and they continued to send the old tests.

We ended up asking HR to filter out some of the least eligible people while we go for most eligible but we had to be explicit to the team receiving resumes to make they they didn't discard people who didn't get a degree but have the necessary experience (since I'm in that bucket along with 1/2 the team).

Ultimately, after we receive the resumes, we then tell HR to send the "Attached" document to the applicants which avoids triggering the "Oh, they just want the test sent and i already have a copy I can send out".

And, we do put existing people back through the tests. It helps us work out what training we need to provide or get feedback on revising the questions.

Comment: Re:Can't Tell Them Apart (Score 1) 466

Working for you must be interesting.

The test we wrote specifically apply to the skill-sets we need:

  • - SQL Aggregates based on various join types and date ranges. In some cases, asking for rolling totals or even giving questions which cannot be answered accurately. For the later case, we are looking to see either what type of "best effort" they make or what questions they ask to find out more about what we are trying to do vs what we are asking to have done.
  • - Diagnosing a block of code based on a specific "Error Message" to look for it's actual cause and evaluate other areas which may cause bugs. I like to add 1-2 non-obvious issues.
  • - Identify differences between types of the technologies we use (specifically listing the technologies and the limited scope for the review).
  • - Provide a problem domain, identify available toolsets and environments, then ask for 1-2 generic solutions along with possible risks. We keep this generic to reduce the risk they will come up with dumb solutions thinking we want steal their ideas.

We rarely use them as "Pass"/"Fail" questions but grade each question on a 1-10 scale of the answers provided then find the people with the better score. Comparing that to the interview itself helps us decide who we want to interview again with management. We have overridden our scoring system on occasion because someone impressed us on a question but didn't get the highest score. Their answer was sufficient to allow us to make a judgement call. Worked out rather nicely based on the skills they brought that we didn't make a test to measure.

We also change the questions based on how our work changes so that we don't try to test against something we were doing 3+ years ago but aiming for skills we need now or will need in a few months.

Comment: Re:Tired... (Score 1) 860

by DaWhilly (#46409361) Attached to: Microsoft's Attempt To Convert Users From Windows XP Backfires
You mean the WebKit? http://en.wikipedia.org/wiki/W... "WebKit is available under a BSD-form license [10] with the exception of the WebCore and JavaScriptCore components, which are available under the GNU Lesser General Public License." Apple is evil for requiring everyone to use a non-proprietary rendering engine in their iOS browsers (that they also use in their non-iOS browsers). Shame on them!

Comment: maybe this applies (Score 1) 716

by DaWhilly (#46227203) Attached to: Ask Slashdot: Should Developers Fix Bugs They Cause On Their Own Time?
A brick layer who notices the wall falling apart and keeps building is doing it for several possible reasons, here are the two major ones I consider: 1) Fraud - they want to get the wall built, be paid, and get the hell outta Dodge before someone notices (Malicious intent) 2) Incompetent - they don't notice the wall falling apart. 3) Directions - their boss tells them to keep building despite the bugs. If #1 applies, the boss is to blame for hiring the guy/gal and not monitoring the work quality. If #2 applies, the boss is to blame for hiring the guy/gal, not monitoring the work quality, and giving the employee work beyond their skillset. if #3 applies, the boss is to blame for ordering the guy/gal to keep developing despite the issues occuring. In each case, you'll notice the Boss exists to provide direction. If the Bricklayer doesn't have a boss, then, yes, they are to blame. If the Bricklayer has a boss, the boss is to blame. Authority is responsible when subordinates screw shit up.

"But this one goes to eleven." -- Nigel Tufnel

Working...