"you're going to hate me"
this talk is "badly substantiated" and "not what you want to hear"
"please leave now"

recruitment is very thorough
everyone invests a lot of time


typical procedure
	1. cv selection / headhunting
		throw away 50% of CVs without reading
		-> "I don't want unlucky candidates" (huge laughter)

		selection is based on skills- and team-matching

		key factors:
			visible work
			skills per unit of time

	2. first interview
		CV sanity check: would I like to work with this person

	3. second interview
		done by COO and pierre
		interviewee is under pressure to answer open and difficult questions
			no good answers
			definitely bad ones
		"we can't do it, and they ask if they can; what do you say?"

	4. technical test
		here's a need; write code in 2hr

Perl Developer's profile
	love perl
		discovered by accident, never looked back
	have an imac, ibook, and ipod
	irc is my life
	my social lie is Perl (buffybuffybuffy)

we have distinctive traits:
	open source is good
		"I agree"
	close source is evil
		...except Apple's code
	all software should be free
		"dream on"

	the cpan release controversy
		"you must have released a useful cpan module"
	if you haven't released one and you want to apply, just release one
	if you don't like the rule, don't apply

	we love perl
		romantically (that's cute)
	we hate other languages
		the M$ conspiracy (that's immature)
	
	know what $_[0] means

	software development is an art
	using perl is not an excuse for not knowing the art

	perl is powerful
	with great power comes great responsibility

	perl is not about software development
	swdev is about problem solving with a computer
	read schwern's slides
	read mspress books

	knowledge++
	(ability to learn)++ ++
	(learning)++ ++ ++

	perl developers are interested in how to solve problems in perl
	that's ok if you can explain it in plain english

	perl developers are less interested in solving problems w/o perl
	"how do you explain it to your grandmother?"
	if you can't, you don't konw what you're doing
	
	can you tell grandma what an object/interface is?
	what would be the right API for a camel?

	the solution is the easy part
	perl developers tend to do it well

	we don't identify the real problem well or decompose it well

	other developers /must/ because their language "is rubbish"
	we must do it anyway