Coding quality, understanding the bigger picture and knowing where to ask help.
Asking anyone an aptitude question will tell you one of two things. They got it right or wrong. However, just because you don't have the same answer as they do, doesn't mean either of you are wrong.
We have an aptitude test, and one of the questions is 'Where would look to find help?'. The hoped answer from the originator of the question was 'perldoc'. However, I tend to use CPAN PODs and O'Reilly books much more.
Another thing to think about is that you shouldn't be trying to trip people up, but get them to tell you their limits. When you know someone has a limit, you then know what areas of knowledge you can impart to them.
Another question was to write a closure. I personally hadn't written a closure until I read Damian's OO book and discovered how cool they were. I wonder how many experienced non-OO programmers there are who haven't a clue what a closure is?
Birmingham Perl Mongers
Web Site: http://birmingham.pm.org/
Actually, it's more of "how many non-functional programmers who don't know what a closure is". Or, as a friend of mine put it, "Perl lets you do everything you'd want to do that LISP does, but without making it look like the language is hacked."
------ We are the carpenters and bricklayers of the Information Age.
Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.
Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.