Skip to content
0:00 / 0:00

#python#cpython#pep8

Raymond Hettinger, "Being a Core Developer in Python", PyBay2016

SF Python

19K subscribers • 6 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • A classic. People kept recommending it from 2020 to 2024.
  • Presented by Raymond Hettinger, Python core developer
  • Linked in the descriptionSlides on Speaker Deck
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

50K views10 years ago2 recommendations

Programming languagesTools and practicePythonLanguage design and type systemsRefactoring and legacy code

Raymond Hettinger shares lessons from fifteen years of Python core development, discussing stability, refactoring, and user-centric design.

PyBay 2016 Keynote What I've learned from being a maintainer and core developer for the past 15 years. Thoughts on channeling Guido, stability, hyper-generalization, Sturgeon's law and egativity, evaluating submissions, inability to predict the future, user centric design, treating mature code differently, believing in or doubting your predecessors, lever arguments and completers, problems of too many choices, implementation details, how much to document, needs of the standard library versus the needs of users, code that is dead on arrival and how PyPI changed everything, orthogonality, importance of skill and expertise, consistency and foolish consistency, optimization and premature optimization, security tautologies, argument ordering, operator abuse, avoiding race to implementation (we can all write working code), the naming of parts, economy of force and complexity balance, feature creep, developing for others, over reliance on Guido, great minds don't think alike, preference for compactness, and aversion to deprecations. What it means to be completely reliant on long term unpaid volunteers. Bio: Raymond has been a prolific contributor to the CPython project for over a decade, having implemented and maintained many of Python's great features. He has been instrumental in modules like bisect, collections, decimal, functools, itertools, math, random, with types like namedtuple, sets, dictionaries, and in many other places around the codebase. He has contributed to the modification of nearly 90,000 lines of code in the CPython repository, and has made over 160 changes in the PEP repository. Raymond has also served as a director of the Python Software Foundation, and has mentored many people over the years on their contributions to the python-dev community. He's also well known for his contributions to the Python Cookbook, and shares many pieces of Python wisdom on Twitter. He received the Distinguished Service Award at PyCon 2014 for his exceptional contributions to the python community. ​ speakerdeck.com/pybay2016/raymond-hettinger-keynote-core-dev… ​

Why it's here

2 people recommend this

What people say. Recommended as an insightful talk on software maintenance, warning against refactoring for its own sake and explaining core developer perspectives.

Moments people linked to

u/pstomiin r/programming • Recommends

On “Goodbye, Clean Code”

To put this into perspective, two videos by Raymond Hettinger (a famous python core developper) come to my mind: * Being a Core Developer in Python where he says: "Don't be a picture straightener", i.e refactoring for the sake of refactoring (or code beauty) can sometimes be less than helpful. You should assume that the person who wrote it might have known what she was doing. * Beyond PEP 8 where he says that you should not forget the big picture. If you are in a state of mind where you only improve the code layout for example (or any specific topic without thinking of the project as a whole), your "refactorings" might miss the elephant in the room where a simple design adaptation mi…
1View on Reddit

u/ManyInterestsin r/rust • Recommends

On “Rust for Linux maintainer steps down in frustration”

I think the resistance is wholly predictable. Raymond Hettinger explains this in the context of being a core developer for CPython. I think the same principles he talks about in that 'be a good neighbor' section have the same underpinnings as in the Linux world and the resistance of their maintainers.
1View on Reddit