Created
September 29, 2012 17:26
-
-
Save jnoller/3804651 to your computer and use it in GitHub Desktop.
Why your employer Should send you to PyCon
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| LINKS: | |
| https://us.pycon.org/2013/about/what-is-pycon/ | |
| http://juliaelman.com/blog/2012/mar/13/my-first-pycon/ | |
| http://pydanny.blogspot.com/2011/01/why-you-should-go-to-pycon.html | |
| http://jessenoller.com/2011/09/23/pycon-2012-sponsorship-making-the-case-for-sponsorship/ | |
| https://us.pycon.org/2013/sponsors/whysponsor/ | |
| Goal of this document: Provide a compelling case for why companies should send their employees to PyCon. Ideally tie into stories like this: http://pycon.blogspot.com/2012/09/pycon-us-2013-highlighting-aweber.html and http://pycon.blogspot.com/2012/09/pycon-us-2013-highlighting-dreamhost.html | |
| This document will be converted to markdown/html and posted to the PyCon website and the PyCon blog. | |
| ============= |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PyCon provides extremely cost effective training. For the cost of a typical training program ($1,500) attendees have access to a wide variety of tutorials, presentations and discussions. Add onto that access the authors of libraries and tools they use and you have some very compelling reasons to attend PyCon.