Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
A friend of mine has been asked to complete the following pre-phone interview test.
FFS you wouldn't ask a bloke to come round to fix your car stereo then make before he starts make him rewire your great grandfathers gramophone just to make sure he was suitable....
would you do it? I told him to tell them to fek orf
Please write a small application that can calculate the difference in days between two dates.
The application should meet the following requirements:
• It should be written in C# and .NET
• The code must not use the DateTime or other date functionality provided within the .NET library, this is a test of coding, not of knowledge of the .NET FCL
Simple.
Step 1
Use .NET Reflector to get the source code of the M$ DateTime classes.
The more I think of it, the more I think it's not such a bad test of coding. A less horribly contrived one would be of course.
You'd end up with about 1 screen's worth of code, and you'd be able to see how well factored it was, what the guy's commenting was like etc; whether he's from the 'keep it simple' or the 'OO purist' school of thought etc.
A friend of mine has been asked to complete the following pre-phone interview test.
FFS you wouldn't ask a bloke to come round to fix your car stereo then make before he starts make him rewire your great grandfathers gramophone just to make sure he was suitable....
would you do it? I told him to tell them to fek orf
I would do it at a charge, to be detracted from the first invoice if they hire you
The application should meet the following requirements:
• It should be written in C# and .NET
• The code must not use the DateTime or other date functionality provided within the .NET library, this is a test of coding, not of knowledge of the .NET FCL
• The code can be as complex or as simple as you think is needed to meet the requirements.
• The code must be able to be compiled, run and tested.
• The code should be supplied in a Zip file
I would knock it out in as small and efficent a program as was possible and when they came back to me tell them where to stick thier job. When they ask why tell them because of the stupid menial testing process that they made me do and I would make it clear that any professional would see something like this as a huge insult.
The code must not use the DateTime or other date functionality provided within the .NET library, this is a test of coding, not of knowledge of the .NET FCL
A good coder would use the library. End of.
It's a crap, dull, pointless and tedious test. Your friend should refuse to do it.
Leave a comment: