After throwing down a few code tests I've started to have some ideas about what I want to see in a code test submission.

1. How to pass a ruby code test
Robert Postill

2. Huh?

3. Mea Culpa

4. No names

5. http://github.com/C3/code_test

6. Habits

7. Junior

8. No Objects?

9. No tests 

10. Train Wrecks
thing.method.fiddle_result!.sort.fiddle_more
things.block {|yielded_thing|
15 lines …
possibly including block
}.mangle
IO.risky_operation.immediately_bugger_about_with_result

11. Ignore the standard library

12. No Gemfile

13. No Rakefile

14. No documented thinking

15. Show me you thought about the
problem. That’s it.

16. Journeyman

17. Object Design

18. It only runs on Windows

19. Make it complex to run
bin/app –fiddly-flag –J –see-
output

20. Use select, collect, reject and
inject
Bonus fail points for all on one line

21. Give me an aesthetic sense
Make it easy to run
Design with objects
Have some basic tests
Show some environmental sensitivity

22. Craftsman

23. Don’t make a
gem/redistributable package

24. Extend object

25. Do something tricky like ASCII
bit-twiddling

26. Rely on an implementation bug

27. Go crazy with symbol to proc

28. Don’t consider object side effects

29. Don’t use large scale code
organisation like modules

30. Wow me with:
a git repo
a thorough test suite
some description of your thinking
well organised files

31. How to get up the curve?
Books:
Clean code: A Handbook of Agile Software
Craftsmanship
The Little Schemer
Structure and Interpretation of Computer
Programs
Ruby Group
Contributing to projects

32. Questions?
Photo Credits
Turtle - http://www.flickr.com/photos/hyakuhei/2234810476/
Witch Burning - http://www.flickr.com/photos/marsumic/4384582059/
PHP rock stars-
http://www.flickr.com/photos/rbowen/2523308528/
Ninjas –
http://www.flickr.com/photos/osakajock/121838967/