Gur Mra bs Clguba, ol Gvz Crgref
by Aravind Krishnaswamy (speaking)
Objective
First, take a look at the lines of code below.
s = """Gur Mra bs Clguba, ol Gvz Crgref
Ornhgvshy vf orggre guna htyl.
Rkcyvpvg vf orggre guna vzcyvpvg.
Fvzcyr vf orggre guna pbzcyrk.
Pbzcyrk vf orggre guna pbzcyvpngrq.
Syng vf orggre guna arfgrq.
Fcnefr vf orggre guna qrafr.
Ernqnovyvgl pbhagf.
Fcrpvny pnfrf nera'g fcrpvny rabhtu gb oernx gur ehyrf.
Nygubhtu cenpgvpnyvgl orngf chevgl.
Reebef fubhyq arire cnff fvyragyl.
Hayrff rkcyvpvgyl fvyraprq.
Va gur snpr bs nzovthvgl, ershfr gur grzcgngvba gb thrff.
Gurer fubhyq or bar-- naq cersrenoyl bayl bar --boivbhf jnl gb qb vg.
Nygubhtu gung jnl znl abg or boivbhf ng svefg hayrff lbh'er Qhgpu.
Abj vf orggre guna arire.
Nygubhtu arire vf bsgra orggre guna *evtug* abj.
Vs gur vzcyrzragngvba vf uneq gb rkcynva, vg'f n onq vqrn.
Vs gur vzcyrzragngvba vf rnfl gb rkcynva, vg znl or n tbbq vqrn.
Anzrfcnprf ner bar ubaxvat terng vqrn -- yrg'f qb zber bs gubfr!"""
d = {}
for c in (65, 97):
for i in range(26):
d[chr(i+c)] = chr((i+13) % 26 + c)
print "".join([d.get(c, c) for c in s])It's nice to know what the output is, but that's not the point.
Attend this session, and you'll understand why the output of this program matters.
Description
This session will talk about 'The Python Way', the guiding philosophy that's a part of every line of code we write.
- What do the lines mean?
- Why do they matter? Are there some that you disagree with?
- If there was a 20th line, what would it be?
- How can you incorporate this philosophy into what you do?
Requirements
Hmm, a state of Zen perhaps?
Speaker bio
I'm a hands on entrepreneur and tech executive.
2
▼
Readability counts ? :)
1
▼
Isn't this proof of the original sin? :)
1
▼
Tip: Use http://decode.org/
;)
2
▼
Did you really need to import that? :)
1
▼
We should get more details on the description on the talk. The current description is vague. The speaker bio should also be updated to explain why you are a better person to give this talk.
1
▼
I'm certainly not the best person. But I'd like to think I'm a strong candidate since I'm passionate about this topic. If there's a better candidate, by all means let them take it up.
I spoke at Pycon 2013 for the first time last year and blogged about my experience - My First Pycon. Here's also the video.
From the post conference feedback from the organizers as well as tweets online, my perception is that the session was well received.
However, I personally felt I had crammed too much into the session, and wanted to focus on a more specific topic this year.
My submission this year was intentionally vague. Like Arun pointed out, it's not too hard for someone to figure out what the output is about. But my focus is on diving to the why behind the Zen. I'll cover a bit of history, specific examples of best practices and bad ones, a question around the original sin in python, and challenge the ongoing relevance of some of the items in the Zen list.