this talk is given by the guy who gave debugger talk

note to self: always set up a way to hit one key to move back/forward in slides
no clicking in specific area

projects start small, and might not grow if the code is a mess

large isn't just TLOC
or number of developers

what is style?
	not just varnames
	guidelines to make code easier to read understand and maintain
	programming standards and conventions
	read code complete

some of Perl's features make it an awful language for large organized projects
perl encourages tmtowdiism
doesn't discourage cowboy coding
	galloping off on your own
	unnecessarily dense code (false hubris)
	reinventing the wheel unnecessarily (false impatience)
	brute-force programming (false laziness)

style guides
	start with a short guide, grow your own
	stick to a guide; a guide is better than none
	project manager is the Keeper Of The Guide
	some projects have their own
		slash
		ensembl