Keynote - Preventing, Finding, and Fixing Bugs On a Time Budget | Raymond Hettinger @ PyBay2018

This talk was presented at PyBay2018 - the Bay Area Regional Python conference. See pybay.com for more details about PyBay and click SHOW MORE for more information about this talk.
Speaker Bio
Raymond is the leader of an international Python training and consulting company and a celebrated speaker in the Python community worldwide. He has been a Python core developer for 16 years, contributing extensively to modules like bisect, collections, decimal, functools, itertools, math, random, with types like namedtuple, sets, dictionaries, etc. He is also known for his contributions to the Python Cookbook and for teaching Python via Twitter. He has also a recipient of Python Software Foundation's Distinguished Service Award.
This and other PyBay2018 videos are brought to you by our Gold Sponsor Cisco!

[@karlbooklover]

I see a talk from Raymond -> I click, simple business

[@dannydk6]

Raymond, you have mastered a magnificent balance of technical expertise and clear/concise communication. Love your talks and conferences man, I’ve learned so much!

[@cordularaecke]

Viewing Raymond Hettinger as an educator and entertaining speaker? (Bangs table) ... No, there isn't a better way😉

[@r3ap3rpy]

I love his talks. He makes me believe that I can learn, do, understand anything.

[@kevinhock1041]

Raymond's the best

[@SiphoMkhwanazi]

Raymond you're the best sir.

[@arnoldwolfstein]

Almost, if he wouldn't use emacs instead of vim.

[@piotrwln9348]

God I love that guy (as a speaker of course!).

Slides here: pybay.com/site_media/slides/raymond2018-keynote/intro.html

[@mytelevisionisdead]

Interesting little insight on the 3-means voting patterns!

[@aoeu256]

Hmm, its so easy to use Hy to convert those doctests into temporary static types so that you can use mypy. The algorithm is simple, when you see a list in a doctest it stands for a Sequence, when you see a set its an UnorderedSequence, when you see an integer it stands for a Number, when you see a float it stands for a float, when you see a str it stands for a str, when you see an Object it stands for Object (if you set the __astype__ attr in Object and it uses that type instead of the object), when you see a dict it stands for dict. What do you guys think? Also mypy should have IDE intergration where it tells you what type it thinks something is.

[@RoamingAdhocrat]

cutting and pasting from the interactive prompt to the docstring is all well and good unless you've spent an entire afternoon trying to get an up-to-date (YouCompleteMe-compatible) build of Vim installed, and configuring the makefile to turn on "paste from system clipboard" has entirely defeated you

[@Asdayasman]

Isn't hypothesis just reimplementing your functions? Why is that useful?

[@DanHaiduc]

It's not reimplementing. You implement constraints over them. The example in the talk was a quadratic equation solver. The code finds the equation roots, but the testing plugs those roots back in and sees that they output near-zero. I have a different example: if you're implementing an encode -> decode pair of functions, then you can test that decode(encode(x)) == x. Or you can test that no matter what input you get, your function does not crash (by simply calling it). It's implementing "constraints", not re-implementing the code.