Solving problems by sharing them... with Python!
summary
Argues that sharing runnable artifacts and visual evidence reduces manager-developer disconnect, showing concrete wins: uses ipython notebook to load model output, plot a sea‑breeze time series and demonstrate the claimed pattern is absent; runs PyPy performance history with CodeSpeed; provisions with Vagrant and Salt and shares gists and screencasts. Cites a surprising industry figure $312 billion annual debugging cost and replicated studies where higher monetary rewards worsen cognitive task performance.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:26Developers
- 3:25Evolution
- 7:40Planning Decisions
- 8:54Being Different
- 10:10Bringing it Together
- 10:51Frustration
- 11:29The Dunning Kruger Effect
- 14:20The antidote
- 15:00The science
- 20:17Autonomy mastery purpose
- 25:53Disconnects
- 29:18Diversity is a solution
- 31:40Python is doing it right
- 31:51Gain credibility
- 32:26Examples
- 35:01Notebooks
- 37:37Bridging the distance
- 38:40Sea breezes
- 40:09The Blue Line
- 41:24Restart Presentation
- 41:37Five Second Overview
- 43:54Summary
related talks
48mWhither Problem-Solving Environments?
41mBetter Code for Data Science
01h 23mImproving Your Data Modeling Work Through Open-Source Software
51mProgramming is Debugging
42mSimplifying Data Analysis with GitHub Codespaces, Jupyter Notebooks & Open AI
33mSignificant Roadblocks to Usefulness for Jupyter Notebooks and a Recipe to Fix them
24mDispelling The 'Genius Programmer' Myth Through Code Review
01h 06mSaturday: Lightning Talks