Dual Core: If John can solve difficult programming puzzles then John can learn whatever is needed for the job if he doesn't already know it.

Kobojunkie:

Wrong!! I know first hand that is not the case.

[b]Programmers who are well versed in logic and algorithm analysis skills are not necessarily the best programmers, and are certainly not all able to learn all that is necessary to get the job done. Many of 'em are simply very good at handling those quick task, such designing solutions for complex problems. However, when it comes to sitting down to code websites which require commitment and long hours, tackling the many, for lack of a better phrase, 'mundane tasks' that many so-so programmers are used to, they find it hard to deal.

Companies that majorly suggest puzzle solving are companies that are looking for people who are able to provide quick solutions/patches needed for mainly complex applications, not your run of the mill website project.
Web Developers don't really require puzzle solving skills. . . . I mean 70% of the times, once you have coded one website, you can code em all.It would be great if you could find someone who has ability to solve puzzles but also settle for the typical tasks. [/b]

Some of my colleagues are very good puzzle solvers . . . . but when it comes to coding your typical application, I would rate many of them a 4 out of 10. One seems to have answers for most every situation but has a hard time sitting down to actually code up the very same solutions, yet he is a brilliant dude.

Wallie:
Speaking of puzzles and brain teasers...

What is the number that is 5 times the sum of its digits?

Fayimora: lol @Beaf One answer is 45! I wrote a small paper on this.

techytom: If I want to employ a programmer, the first thing I'll check is experience, not job experience but the candidates programming experience. I want to be sure the programmer can do what he says he can do. So I'll keep him as comfortable as possible and the results of him talking about his skills and past experience helps me bring up a test for him. I'll then judge based on problem solving approach, code/software practices, if he's a programmer(neatness of code), software engineering(approach to information gathering). I don't want to be one of the folks that put programming and software engineering as the same so, I'll watch out for architects and black screen coders...

Seun: @Fayimora: Thanks. Isn't a web developer a type of programmer, though?

Fayimora:
In a logical sense, yes! #1 => [However, we must respect the fact that a web developer would not spend time analysing a project as that is the job of an analyst]. Also, a web developer [#2 => [ would not be expected to always solve problems [/b]using Advanced Algorithms and stuff like that. That is something a programmer would be interested in.] [b]I think we are just twisting words here tho. Its always best to pick what you need. #3 => [Trying to pick the best could get you in trouble.] .....

@delomos @techytom you can't pick a good programmer based on what he or she has done.#4 => [ You are better off using School projects or ACTUAL work experience.] Reason is that, # 5=> [as a programmer, you have a lot of time to build your own software! No deadline, no criteria, no limited specs as you just add to your project what you feel like and so on. Does that really define your software developer?] #6 => [One thing I also think is lame is asking developers stuff like "what is a framework?", "describe the MVC architecture" and so on.]

#7 => [ -> Do they fit into the community?? [optional] <= don't know how relevant this is so wont say anything ]

#8 => [ Truth be told, all you really need is someone that gets the job done!]

jeebz: Programming tests are relative i.e depending on the role and the company software product.

techytom: if he's a programmer(neatness of code), software engineering(approach to information gathering). I don't want to be one of the folks that put programming and software engineering as the same

delomos:
it's a waste of time bringing an engineer in for interview and asking them to "code".

Fayimora:
-> Do they fit into the community?? [optional] <= dont know how relevant this is so wont say anything

delomos:
#7. This is wickedly important (assuming you're referring to your company culture) -- I always hope to work with folks I can hang out with out of the office.

csharpjava:
#1 => I'm sure that both of you have never met a qualified Software Engineer before, because if you have then you won't make such comments. Software Engineers are trained to handle all stages of software development life circle, which includes programming. Ok here is a simply programming test for a Software Engineer, you can try it yourself.

#2 => Question: Convert the class diagram below to a Formal specification that will guarantee that the code will not fail and then convert each line of the Formal specification to either Java, C# etc. An extract of the Formal specification has been provided for you to complete.

okeyxyz:
@delomos, while your emphasis that this is wickedly important is correct but your underlying reason is misleading. your interest in being able to socialize outside of the workplace is surely a good thing, but it's a bonus rather than the principal reason for fitting into the work community. having the pleasure of choosing people of like mind as yourself is what social scientists call groupthink and the dangers of this mindset is that it promotes mono-culture within the team, does not challenge status-quo and stifles innovation.

fitting into the community is about being able to work with persons of different backgrounds(business-role, age, sex, race, religion, social-status, cultures, etc) to build an innovative and business-successful team, it's about making efforts to understand what the greater society (for whom you will be developing/building products) needs, and it goes a long way to help if that society is represented in the team, thus this is a management specialty to promote a work environment that harmonizes and harnesses the experiences, expectation & talents of these varying backgrounds to build that product which meets all needs. it's about working in a team rather than in a group, and this means working with people different from you.

so how you embrace this principle will determine how your product/company performs in a fiercely competitive & globalized economy.

delomos: @csharpjava
#1. You made a very bold statement, "...you are sure"? I'm tempted to ask how sure you are but that will digress my point.

Apart from being quoted out of context, my original statement you didn't agree with is: "Per my ogas, it's a waste of time bringing an engineer in for interview and asking them to "code"." Which was a follow up from: "Given X problem, how would you approach it (X being a problem the team is currently working on and as pointed by @techytom the process is a lot more important than the answer)."

#2. Perhaps that answers your question, maybe not, people who are sure about people they never met are rather strange people to have logical conversations with, or maybe not...

#3. It's easy to show nice looking symbols and UMLs and theorem -- it generally explains why we have Professors and people solving real problem. Maybe that was a bit too poetic. I must commend digging up that picture, it indeed looks interest, I will print it out and show a Software Engineer if I'm ever lucky enough to meet one.