Tjoker
Expert Member
Actually it is. Microsoft just promised not to sue anyone who wants to copy the specification.
lol
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Actually it is. Microsoft just promised not to sue anyone who wants to copy the specification.
Refactored!While ((worker.Salary <= Insult) || (worker.Role == Slave))
{
worker.move(overseas);
}
After taking a moment to chill, I came to a conclusion. I do not envy anyone trying to recruit developers. We're an impossible bunch.
After taking a moment to chill, I came to a conclusion. I do not envy anyone trying to recruit developers. We're an impossible bunch.
+1Programming requires a certain amount of aptitude which cannot be learnt IMO. You either have what it takes to be a programmer or you don't.
Generally the type of people who require spoon feeding don't make good programmers. You can show them how to do something 10 times but when one variable or parameter is changed they come begging for help again.
Personally I like the technical tests - people lie and its a good way to weed them out. It gets employers a better objective picture of your skills.
What I dont like is technical tests that are too narrow in focus - for instance tests that you either know a particular thing about technology X that Bill Gates offhandedly mentioned on the 21st of March 2007 or you dont get the job. Good technical tests will test the scope of your role in a broad fashion but then also contain some highly technical questions to separate the good from the excellent. Plus, I like the idea of having brain teasers, to give them a better idea of how you think. My current company did that, and its a good idea. Its more important how you learn and solve problems than whether you know the names of every static class in the System.Net library.
I agree some sort of way to guage a persons ability and train of thought should be administered, but every test I have taken was very detailed. Lets admit it most of us depend on Google to show us in the right direction. I am sure the company just gets the test from the internet. When I was interviewing candidates, I was asked to give them some sort of test and what I did was show them a piece of badly written code and asked them to comment on it. The other test was a common problem and asked the person to provide a high level solution and that worked for us. More importantly is team work, attitude and aptitude.
Corrected![]()
+1You can generally get the persons grasp from presenting them with a scenario(s), even verbally is fine as generally if a person can grasp the concept and detail thier solution, touching on code, especially if you Q&A and they can discuss the shortfalls of certain methods or substantiate why they would do something, then you can assume they have a grasp on the technology. Syntax and technical errors are common and easily overcome with either applied research or experimentation with the code, the ability to not understand a spec and break it down , is a much larger problem.
What I find is missing in the industry is developers, most people we interview and employ just want to be code monkeys. There is a very big distinction. Developers want to learn the systems, think on what parts a change will affect and then recommend possible solutions. A coder wants to be told exactly what to do and then show him how to do it, every single time.
Knowing the business or the industry you develop for is also where the money is. Don't get me wrong, there are lots of technically challenging projects out there, but its being able to recommend changes to business processes where you prove your worth to a company. Unless you want to stay a code monkey...!
It's simple. Pay sucks, and companies rather outsource overseas (especially India it seems)... I know a few VERY good developers that left the country.
Developers want to learn the systems, think on what parts a change will affect and then recommend possible solutions. A coder wants to be told exactly what to do and then show him how to do it, every single time.