ProveIt!
-
rollei35guy wrote:
wannabe axe-murderers
I now have this image of someone standing over their victim, reading instructions on how to hold the axe :doh:
Visit http://www.readytogiveup.com/[^] and do something special today.
Trollslayer wrote:
I now have this image of someone standing over their victim, reading instructions on how to hold the axe
They've already been tested on that or they wouldn't have gotten the job. :~
Simply Elegant Designs JimmyRopes Designs
Think inside the box! ProActive Secure Systems
I'm on-line therefore I am. JimmyRopes -
- People that are skilled and have a job probably don't do these tests.
Wout
wout de zeeuw wrote:
- People that are skilled and have a job probably don't do these tests.
:doh:
Simply Elegant Designs JimmyRopes Designs
Think inside the box! ProActive Secure Systems
I'm on-line therefore I am. JimmyRopes -
The really funny part is for all 39 questions on the SQL test, I just guessed. If I got 14 right just by guessing, it seems to me that given real-world exposure to the technology would increase my knowledge of it 10 fold. Besides all of that, the two jobs I've had that needed database work done had DBAs on staff to do the intricate stuff (connection strings, creating tables, triggers, and such), and the C++ coders wrote stored procs (or in-code SQL) to handle specific requirements of the C++ code they were writing. IMHO, that's the way it should be.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001John Simmons / outlaw programmer wrote:
Besides all of that, the two jobs I've had that needed database work done had DBAs on staff to do the intricate stuff (connection strings, creating tables, triggers, and such), and the C++ coders wrote stored procs (or in-code SQL) to handle specific requirements of the C++ code they were writing. IMHO, that's the way it should be.
Exactly! I started a new contract last Monday. The interview was purely around why and how I undertake tasks and solve problems. He didn't ask me a single 'technical' question. He was an ex-Microfty. Don't know if that had anything to do with his interview technique but I certainly felt I was allowed to sell myself. Bottom line, if you don't have a clue it'll come out fast enough. Good luck finding a gig.
-
Gary R. Wheeler wrote:
That's a load of crap. Look at my resume, check my references to validate it, talk to me to ensure I'm not a complete dick, and then make me an offer or tell to me to get lost.
I agree. I told the guy I had a) 27 years experience as a programmer, b) taught myself pascal, C++, and pretty much everything else I've needed to know to do the job, and c) had little experience with the .Net framework and almost none for MSSQL of any vintage. The tests I took just proved what I said. I got all the "programming" questions for C# right (only 4 or 5 actual programming questions at the beginning of the test), but had to guess at a lot of the .Net framework stuff. The guy that I interviewed with gave me the impression that researching answers was not an acceptable practice (which is absurd when you're a programmer).
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001John Simmons / outlaw programmer wrote:
he guy that I interviewed with gave me the impression that researching answers was not an acceptable practice
Then he obviously has no idea about being a programmer, bottom line programmers do a ton of research
"Well yes, it is an Integer, but it's a metrosexual Integer. For all we know, under all that hair gel it could be a Boolean." Tom Welch
-
The really funny part is for all 39 questions on the SQL test, I just guessed. If I got 14 right just by guessing, it seems to me that given real-world exposure to the technology would increase my knowledge of it 10 fold. Besides all of that, the two jobs I've had that needed database work done had DBAs on staff to do the intricate stuff (connection strings, creating tables, triggers, and such), and the C++ coders wrote stored procs (or in-code SQL) to handle specific requirements of the C++ code they were writing. IMHO, that's the way it should be.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001John Simmons / outlaw programmer wrote:
Besides all of that, the two jobs I've had that needed database work done had DBAs on staff to do the intricate stuff (connection strings, creating tables, triggers, and such)
Wow, where I work us developers are required to do all that, we write the scripts for the triggers, tables, etc and when the monthly release is promoted the scripts are ran
"Let's face it, the average computer user has the brain of a Spider Monkey." Bill Gates
-
rollei35guy wrote:
wannabe axe-murderers
I now have this image of someone standing over their victim, reading instructions on how to hold the axe :doh:
Visit http://www.readytogiveup.com/[^] and do something special today.
