The Mental Game of Python - Raymond Hettinger [synced version]
Tech Ma2 HN recommenders · recommended in 2 months, 2020–2026
talk · intermediate · evergreen · 2020–2026 on HN
Raymond Hettinger's PyBay 2019 talk on the mental strategies he uses when programming in Python, such as chunking, solving a simpler related problem, and repeating tasks manually until patterns emerge. This version is re-synced with the slides.
HN recommends it as an entertaining talk on how working memory shapes code and how to reduce cognitive load.
Up next
10 mo on HNHamming, "You and Your Research" (June 6, 1995)
securitylectures
11 HN recommender · 2012–2023
3 mo on HNOswald Acted Alone: JFK Assassination Solved (Part 1 of 2)
Sean Munger
4 HN recommender · 2023–2024
18 mo on HNRuby Conf 12 - Y Not- Adventures in Functional Programming by Jim Weirich
Confreaks
17 HN recommender · 2013–2026
16 mo on HNThe spelled-out intro to neural networks and backpropagation: building micrograd
Andrej Karpathy
17 HN recommender · 2022–2025
16 mo on HNHow Python was Shaped by leaky Internals, Armin Ronacher, Flask framework
Видео с мероприятий {speach!
15 HN recommender · 2017–2025
15 mo on HNRailsConf 2014 - All the Little Things by Sandi Metz
Confreaks
15 HN recommender · 2015–2025
14 mo on HNWhat the heck is the event loop anyway? | Philip Roberts | JSConf EU
JSConf
16 HN recommender · 2015–2025
12 mo on HNHow To Design A Good API and Why it Matters
Google TechTalks
12 HN recommender · 2011–2025
12 mo on HNThe Problem with Time & Timezones - Computerphile
Computerphile
12 HN recommender · 2014–2026
10 mo on HNRailsConf 2016 - Turbolinks 5: I Can’t Believe It’s Not Native! by Sam Stephenson
Confreaks
6 HN recommender · 2017–2020
9 mo on HNBrian Goetz - Stewardship: the Sobering Parts
ClojureTV
10 HN recommender · 2014–2025
10 mo on HNRuby Midwest 2011 - Keynote: Architecture the Lost Years by Robert Martin
Confreaks
10 HN recommender · 2013–2022
3 comments from Hacker News
Raymond Hettinger gave an entertaining talk [0] on a related topic. He taled about how the working memory limits are reflected in code, and how we can reduce the necessary cognitive load of understanding a piece of code. [0] ▶ this video
Raymond Hettinger is such a treasure! He keeps things simple and in the process you actually learn. I tend to overload the registers when teaching and students do not learn as much. All teachers know the feeling when students eyes glaze over, something that is so much harder to detect in the age of Zoom and Teams. PS ▶ this video there is a sync fixed version of the talk
> It's a bit cleaner. That's pretty much the reason why. Raymond Hettinger explains the philosophy well while discussing the `random` standard library module: ▶ this video I feel like much of this has been forgotten of late, though. From what I've seen, i's really quite hard to get anything added to the standard library unless you're a core dev who's sufficiently well liked among other core devs, in which case you can pretty much just do it. Everyone else will (understandably) be put through a PhD thesis defense, then asked to try the idea out as a PyPI package first (and somehow also popularize the package), and then if it somehow catches on that way, get declined anyway because it's easy for everyone to just get it from PyPI (see e.g. Requests). I personally was directed to PyPI once when I was proposing new methods for the builtin `str` . Where the entire point was not to have to import or instantiate anything.