POPULARITY
Categories
490 episodes with Python
409 episodes with Python
304 episodes with Python
205 episodes with Python
294 episodes with Python
189 episodes with Python
357 episodes with Python
126 episodes with Python
88 episodes with Python
97 episodes with Python
195 episodes with Python
88 episodes with Python
65 episodes with Python
106 episodes with Python
51 episodes with Python
62 episodes with Python
54 episodes with Python
40 episodes with Python
52 episodes with Python
102 episodes with Python
43 episodes with Python
101 episodes with Python
60 episodes with Python
46 episodes with Python
53 episodes with Python
35 episodes with Python
42 episodes with Python
34 episodes with Python
58 episodes with Python
39 episodes with Python
28 episodes with Python
34 episodes with Python
77 episodes with Python
27 episodes with Python
23 episodes with Python
25 episodes with Python
23 episodes with Python
31 episodes with Python
40 episodes with Python
22 episodes with Python
25 episodes with Python
32 episodes with Python
33 episodes with Python
33 episodes with Python
15 episodes with Python
29 episodes with Python
47 episodes with Python
26 episodes with Python
20 episodes with Python
45 episodes with Python
23 episodes with Python
15 episodes with Python
40 episodes with Python
15 episodes with Python
BACK ON FIGG EP 346 Python P Learn more about your ad choices. Visit megaphone.fm/adchoices
Mike ‘Trapper Mike' nee ‘Python Cowboy' Kimmel joins Robbie on the podcast recorded on-location in sunny South Florida. Mike, who has made a name for himself as a prolific python catcher using German wire-haired pointers, talks about sustainability, invasive species, and what drives him to hunt. Get to know the guest: https://www.instagram.com/pythoncowboy/?hl=en Do you have questions we can answer? Send it via DM on IG or through email at info@theoriginsfoundation.org Support our Conservation Club Members! Maartens Safaris: https://maartenssafaris.com/ Grayl: https://grayl.com/ The Sun Project: https://theoriginsfoundation.org/conservation-projects/the-sun-project/ See more from Blood Origins: https://bit.ly/BloodOrigins_Subscribe Music: Migration by Ian Post (Winter Solstice), licensed through artlist.io This podcast is brought to you by Bushnell, who believes in providing the highest quality, most reliable & affordable outdoor products on the market. Your performance is their passion. https://www.bushnell.com This podcast is also brought to you by Silencer Central, who believes in making buying a silencer simple and they handle the paperwork for you. Shop the largest silencer dealer in the world. Get started today! https://www.silencercentral.com This podcast is brought to you by Safari Specialty Importers. Why do serious hunters use Safari Specialty Importers? Because getting your trophies home to you is all they do. Find our more at: https://safarispecialtyimporters.com Learn more about your ad choices. Visit megaphone.fm/adchoices
Do you wake up in the middle of the night, wondering if your business is in the #1 position in AI searches? Join Brad Friedman and Andreas Voniatis as they discuss whether today's SEO playbook is becoming obsolete as people increasingly use AI to research their needs and solutions. They discuss using data science to decode what AI wants to uprank your business everywhere your customers are searching. Andreas Voniatis is the founder of Artios, helping business leaders in ambitious B2B and technology companies achieve breakthrough website results. He's the author of Data-Driven SEO with Python and has been featured in Search Engine Watch. By combining advanced math, data science, and proprietary AI, Andreas says he delivers 3–5x more non-brand organic traffic and guarantees a 2x ROI—far beyond what traditional SEO and content marketing can provide. His journey began when he began thinking that traditional SEO and content marketing were becoming guesswork. Rather than leave the field, he retrained in data science. That shift changed everything — like Neo seeing the Matrix. With Python and new mental models, he began approaching organic growth with scientific precision and scale. The Digital Slice Podcast is brought to you by Magai. Up your AI game at https://friedmansocialmedia.com/magai And, if it's your first time purchasing, use BRAD30 at checkout to get 30% off your first 3 months. Visit thedigitalslicepodcast.com for complete show notes of every podcast episode.
Talk Python To Me - Python conversations for passionate developers
Today on Talk Python, the creators behind FastAPI, Flask, Django, Quart, and Litestar get practical about running apps based on their framework in production. Deployment patterns, async gotchas, servers, scaling, and the stuff you only learn at 2 a.m. when the pager goes off. For Django, we have Carlton Gibson and Jeff Triplet. For Flask, we have David Lord and Phil Jones, and on team Litestar we have Janek Nouvertné and Cody Fincher, and finally Sebastián Ramírez from FastAPI is here. Let's jump in. Episode sponsors Talk Python Courses Python in Production Links from the show Carlton Gibson - Django: github.com Sebastian Ramirez - FastAPI: github.com David Lord - Flask: davidism.com Phil Jones - Flask and Quartz(async): pgjones.dev Yanik Nouvertne - LiteStar: github.com Cody Fincher - LiteStar: github.com Jeff Triplett - Django: jefftriplett.com Django: www.djangoproject.com Flask: flask.palletsprojects.com Quart: quart.palletsprojects.com Litestar: litestar.dev FastAPI: fastapi.tiangolo.com Coolify: coolify.io ASGI: asgi.readthedocs.io WSGI (PEP 3333): peps.python.org Granian: github.com Hypercorn: github.com uvicorn: uvicorn.dev Gunicorn: gunicorn.org Hypercorn: hypercorn.readthedocs.io Daphne: github.com Nginx: nginx.org Docker: www.docker.com Kubernetes: kubernetes.io PostgreSQL: www.postgresql.org SQLite: www.sqlite.org Celery: docs.celeryq.dev SQLAlchemy: www.sqlalchemy.org Django REST framework: www.django-rest-framework.org Jinja: jinja.palletsprojects.com Click: click.palletsprojects.com HTMX: htmx.org Server-Sent Events (SSE): developer.mozilla.org WebSockets (RFC 6455): www.rfc-editor.org HTTP/2 (RFC 9113): www.rfc-editor.org HTTP/3 (RFC 9114): www.rfc-editor.org uv: docs.astral.sh Amazon Web Services (AWS): aws.amazon.com Microsoft Azure: azure.microsoft.com Google Cloud Run: cloud.google.com Amazon ECS: aws.amazon.com AlloyDB for PostgreSQL: cloud.google.com Fly.io: fly.io Render: render.com Cloudflare: www.cloudflare.com Fastly: www.fastly.com Watch this episode on YouTube: youtube.com Episode #533 deep-dive: talkpython.fm/533 Episode transcripts: talkpython.fm Theme Song: Developer Rap
Topics covered in this episode: ty: An extremely fast Python type checker and LSP Python Supply Chain Security Made Easy typing_extensions MI6 chief: We'll be as fluent in Python as we are in Russian Extras Joke Watch on YouTube About the show Connect with the hosts Michael: @mkennedy@fosstodon.org / @mkennedy.codes (bsky) Brian: @brianokken@fosstodon.org / @brianokken.bsky.social Show: @pythonbytes@fosstodon.org / @pythonbytes.fm (bsky) Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Monday at 10am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Brian #1: ty: An extremely fast Python type checker and LSP Charlie Marsh announced the Beta release of ty on Dec 16 “designed as an alternative to tools like mypy, Pyright, and Pylance.” Extremely fast even from first run Successive runs are incremental, only rerunning necessary computations as a user edits a file or function. This allows live updates. Includes nice visual diagnostics much like color enhanced tracebacks Extensive configuration control Nice for if you want to gradually fix warnings from ty for a project Also released a nice VSCode (or Cursor) extension Check the docs. There are lots of features. Also a note about disabling the default language server (or disabling ty's language server) so you don't have 2 running Michael #2: Python Supply Chain Security Made Easy We know about supply chain security issues, but what can you do? Typosquatting (not great) Github/PyPI account take-overs (very bad) Enter pip-audit. Run it in two ways: Against your installed dependencies in current venv As a proper unit test (so when running pytest or CI/CD). Let others find out first, wait a week on all dependency updates: uv pip compile requirements.piptools --upgrade --output-file requirements.txt --exclude-newer "1 week" Follow up article: DevOps Python Supply Chain Security Create a dedicated Docker image for testing dependencies with pip-audit in isolation before installing them into your venv. Run pip-compile / uv lock --upgrade to generate the new lock file Test in a ephemeral pip-audit optimized Docker container Only then if things pass, uv pip install / uv sync Add a dedicated Docker image build step that fails the docker build step if a vulnerable package is found. Brian #3: typing_extensions Kind of a followup on the deprecation warning topic we were talking about in December. prioinv on Mastodon notified us that the project typing-extensions includes it as part of the backport set. The warnings.deprecated decorator is new to Python 3.13, but with typing-extensions, you can use it in previous versions. But typing_extesions is way cooler than just that. The module serves 2 purposes: Enable use of new type system features on older Python versions. Enable experimentation with type system features proposed in new PEPs before they are accepted and added to the typing module. So cool. There's a lot of features here. I'm hoping it allows someone to use the latest typing syntax across multiple Python versions. I'm “tentatively” excited. But I'm bracing for someone to tell me why it's not a silver bullet. Michael #4: MI6 chief: We'll be as fluent in Python as we are in Russian "Advances in artificial intelligence, biotechnology and quantum computing are not only revolutionizing economies but rewriting the reality of conflict, as they 'converge' to create science fiction-like tools,” said new MI6 chief Blaise Metreweli. She focused mainly on threats from Russia, the country is "testing us in the grey zone with tactics that are just below the threshold of war.” This demands what she called "mastery of technology" across the service, with officers required to become "as comfortable with lines of code as we are with human sources, as fluent in Python as we are in multiple other languages." Recruitment will target linguists, data scientists, engineers, and technologists alike. Extras Brian: Next chapter of Lean TDD being released today, Finding Waste in TDD Still going to attempt a Jan 31 deadline for first draft of book. That really doesn't seem like enough time, but I'm optimistic. SteamDeck is not helping me find time to write But I very much appreciate the gift from my fam Send me game suggestions on Mastodon or Bluesky. I'd love to hear what you all are playing. Michael: Astral has announced the Beta release of ty, which they say they are "ready to recommend to motivated users for production use." Blog post Release page Reuven Lerner has a video series on Pandas 3 Joke: Error Handling in the age of AI Play on the inversion of JavaScript the Good Parts
We talk with Matt Trentini, Principal Software Engineer at Planet Innovation, about using MicroPython for professional embedded development—including medical devices. Matt shares how he was drawn back to embedded development after becoming jaded with traditional C-based workflows, and explains why MicroPython's interactive REPL and rapid development cycle have become game-changers for his team.We explore the practical realities of using an interpreted language on microcontrollers: how Planet Innovation uses it for Class B medical devices, what the performance trade-offs actually look like, and how features like the Unix port enable robust testing. Matt walks us through deployment considerations, explains how to integrate C code when needed, and shares compelling stories about real-time client demos that would be impossible in C++.Whether you're skeptical about high-level languages in embedded systems or curious about alternatives to traditional development workflows, this conversation offers a grounded, engineering-focused look at what MicroPython can—and can't—do in production environments.Key Topics[03:30] Matt's background and why he left embedded development before MicroPython brought him back[08:45] What MicroPython is: a complete re-implementation of Python for microcontrollers with REPL, filesystem, and machine module[13:20] How Planet Innovation introduced MicroPython through an OpenMV vision processing project[17:15] The game-changing power of the REPL for interactive hardware development and testing[21:40] Running MicroPython code on x86 for testing, and the mock machine library approach[26:30] Python library compatibility: what works, what doesn't, and memory considerations[29:50] Integrating C and C++ code through extension modules for performance-critical sections[33:10] Performance realities: 10-100x slower in interpreter, but can always drop to C speed when needed[37:45] Tooling: MPRemote, the magical mount feature, and development workflow[42:20] When NOT to use MicroPython: cost-sensitive high-volume products and resource constraints[45:30] Using MicroPython in Class B medical devices and safety-critical applications[49:15] Garbage collection: simple, predictable, and controllable—can be disabled when needed[52:40] Real-time client demo story: modifying state machines during a call and showing results immediately[56:20] Deployment: frozen code, disabling REPL and filesystem, and OTA considerations[01:01:30] Common mistakes: logic errors and inadvertent allocations rather than memory corruption[01:05:45] Threading, AsyncIO, and the Global Interpreter Lock across different ports[01:08:20] State machine frameworks: StateChart, Yasme, and PyTransitions[01:11:40] Junior developer productivity: faster onboarding compared to C/C++ embedded development[01:15:10] Getting started: board bring-up as an ideal first use case for MicroPython[01:17:50] Hardware-in-the-loop testing as a low-risk way to try MicroPythonNotable Quotes"It's hard to overstate how game changing the REPL is. Particularly as an embedded engineer, once you see that you can interactively talk to a peripheral, you can generate your own I2C, squirt it across and see what the peripheral does with it—suddenly driver development has just become easy to experiment with." — Matt Trentini"My trite answer is that MicroPython is slow—10 to 100 times slower than C in the interpreter. But my flip side answer is that it can always be made as fast as C because you can always drop into C to write things." — Matt Trentini"There was a moment in a recent project where we were discussing the workflow of a state machine with the client, and while we were on a call, another engineer was actually making changes to MicroPython code. Literally a couple minutes after we'd been hashing out the details, they showed the changes in the state machine using the REPL. The client was blown away—in 25 years of development, I have never had that kind of turnaround in C and C++." — Matt Trentini"If you want to make a good friend of your electronics engineers, give them a build of MicroPython that can run on their custom board. In the past, they would typically be waiting for weeks or sometimes months before a software resource could be assigned. Now I can turn around a MicroPython build in a day or two, and they can test I2C, GPIOs, and UARTs themselves." — Matt Trentini"The irony is that the people who have embedded C knowledge are actually the people that can benefit the most from MicroPython. It's like having a superpower—you understand what MicroPython is doing in the background, you know you're just effectively writing a lot less code." — Matt TrentiniResources MentionedMicroPython Official Site - The official MicroPython project website with documentation and downloadsOpenMV - Computer vision project using MicroPython for camera-based applicationsMPRemote - Tool for interacting with MicroPython devices, including the magical mount featurePlanet Innovation - Medical device consultancy using MicroPython in production devicesStateChart - State machine library compatible with Python and MicroPythonYasme - Yet another state machine library developed at Planet InnovationPyTransitions - Popular Python state machine library being ported to MicroPythonCircuitPython - Adafruit's fork of MicroPython with additional features and CPython compatibility focus You can find Jeff at https://jeffgable.com.You can find Luca at https://luca.engineer.Want to join the agile Embedded Slack? Click hereAre you looking for embedded-focused trainings? Head to https://agileembedded.academy/Ryan Torvik and Luca have started the Embedded AI podcast, check it out at https://embeddedaipodcast.com/
This is a recap of the top 10 posts on Hacker News on January 01, 2026. This podcast was generated by wondercraft.ai (00:30): Linux is good nowOriginal post: https://news.ycombinator.com/item?id=46457770&utm_source=wondercraft_ai(01:51): Bluetooth Headphone Jacking: A Key to Your Phone [video]Original post: https://news.ycombinator.com/item?id=46453204&utm_source=wondercraft_ai(03:12): A website to destroy all websitesOriginal post: https://news.ycombinator.com/item?id=46457784&utm_source=wondercraft_ai(04:33): Show HN: OpenWorkers – Self-hosted Cloudflare workers in RustOriginal post: https://news.ycombinator.com/item?id=46454693&utm_source=wondercraft_ai(05:54): Cameras and Lenses (2020)Original post: https://news.ycombinator.com/item?id=46455872&utm_source=wondercraft_ai(07:15): iOS allows alternative browser engines in JapanOriginal post: https://news.ycombinator.com/item?id=46453950&utm_source=wondercraft_ai(08:36): I rebooted my social lifeOriginal post: https://news.ycombinator.com/item?id=46453114&utm_source=wondercraft_ai(09:58): Finland detains ship and its crew after critical undersea cable damagedOriginal post: https://news.ycombinator.com/item?id=46456797&utm_source=wondercraft_ai(11:19): ACM Is Now Open AccessOriginal post: https://news.ycombinator.com/item?id=46454763&utm_source=wondercraft_ai(12:40): Python numbers every programmer should knowOriginal post: https://news.ycombinator.com/item?id=46454470&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai
В гостях Лекс Кравецкий - популяризатор науки в области математики и Computer Science, исследователь искусственного интеллекта и его влияния на общество. Поговорим про образование. Извечный вопрос: что не так с образованием? Почему так сложно, когда можно намного проще? Большие языковые модели - это причина необходимости изменения подходов к образованию или лишь катализатор давно назревшей необходимости? Почему в школе учат тому, что легко проверить, а не тому, что было бы, действительно, полезно? Нужно ли начинать изучать программирование с абстракций низкого уровня? Нужно ли всем уметь программировать? Интерес - главный стимулятор образования в любой области, но как понять, что тебе, возможно, станет интересным, если пока совсем неинтересно? Учат ли в школах и ВУЗах учиться? А, может, в школах нужно перестать детям вдалбливать знания, а просто дать возможность играть в компьютерные игры сколько хочется? Почему при устройстве на работу больше смотрят на предыдущий опыт работы, чем на оценки в ВУЗе, но в ВУЗе студенты зарабатывают оценки, а не опыт? А нужно вообще получать диплом в современном мире? Обо всём этом в выпуске!Ссылки выпуска:YouTube-канал Лекса (https://www.youtube.com/@KravetskiLex)Мысли Лекса в ЖЖ (https://lex-kravetski.livejournal.com/)Телеграм-канал Лекса (https://t.me/lexkravetski)Буду благодарен за обратную связь!Подписывайтесь на телеграм-канал "Стать специалистом по машинному обучению" (https://t.me/toBeAnMLspecialist)Мой телеграм для связи (https://t.me/kmsint)Также со мной можно связаться по электронной почте: kms101@yandex.ruЯ сделал бесплатный курс по созданию телеграм-ботов на Python и aiogram на Степике (https://stepik.org/120924). Присоединяйтесь, если хотите научиться разрабатывать телеграм-ботов!Также в соавторстве с крутыми разработчиками я пишу курс по продвинутой разработке телеграм-ботов с элементами микросервисной архитектуры (https://stepik.org/a/153850?utm_source=mlpodcast&utm_campaign=ep_77).Выразить благодарность можно добрым словом и/или донатом (https://www.tinkoff.ru/rm/kryzhanovskiy.mikhail11/NkwE718878/)
En 2025, une nouvelle expression s'est imposée dans le vocabulaire de la tech : le « vibe coding ». Derrière ce terme intrigant se cache une pratique qui transforme en profondeur la manière de développer des logiciels.Le vibe coding, que l'on peut traduire par « programmation intuitive », désigne une approche où le développeur ne code plus ligne par ligne, mais décrit simplement ce qu'il souhaite obtenir à une intelligence artificielle. Popularisé par Andrei Karpathy, ancien responsable de l'IA chez Tesla et cofondateur d'OpenAI, ce concept est né dans les communautés de développeurs avant de se diffuser largement dans l'écosystème numérique.Concrètement, il suffit désormais de formuler une demande en langage naturel : créer un script Python, concevoir une page web avec un formulaire, modifier l'interface d'une application ou même développer un jeu ou une application mobile complète. Cette méthode permet un gain de temps spectaculaire et ouvre la création logicielle à des non-développeurs, capables de produire des outils fonctionnels pour le web, le mobile ou des usages métiers comme des CMS ou des ERP.De nombreux outils incarnent cette tendance, à commencer par GitHub Copilot, mais aussi Cursor, Windsurf ou des assistants généralistes comme ChatGPT, Claude ou Gemini, qui génèrent du code à intégrer ensuite de manière classique. D'autres solutions vont plus loin encore, en produisant directement des applications prêtes à l'emploi, comme le propose la startup suédoise Lovable.Dans cet épisode, Sébastien Stormacq, responsable des relations développeurs chez AWS, partage une expérience concrète : la création, en une heure et sans écrire une seule ligne de code, d'un jeu inspiré de Pac-Man grâce au vibe coding. Un exemple révélateur de la puissance, mais aussi des limites de cette approche.Le phénomène soulève des questions cruciales : qualité et sécurité du code généré, risques de bugs majeurs, mais aussi impact sur l'emploi. Si le vibe coding accélère le travail des équipes et augmente la productivité des développeurs expérimentés, il fragilise davantage les profils juniors. Une chose est sûre : plus qu'un simple outil, le vibe coding redéfinit en profondeur le métier de développeur.-----------♥️ Soutien : https://mondenumerique.info/don
A $20 billion AI deal while you were away?
Talk Python To Me - Python conversations for passionate developers
Python in 2025 is in a delightfully refreshing place: the GIL's days are numbered, packaging is getting sharper tools, and the type checkers are multiplying like gremlins snacking after midnight. On this episode, we have an amazing panel to give us a range of perspectives on what matter in 2025 in Python. We have Barry Warsaw, Brett Cannon, Gregory Kapfhammer, Jodie Burchell, Reuven Lerner, and Thomas Wouters on to give us their thoughts. Episode sponsors Seer: AI Debugging, Code TALKPYTHON Talk Python Courses Links from the show Python Software Foundation (PSF): www.python.org PEP 810: Explicit lazy imports: peps.python.org PEP 779: Free-threaded Python is officially supported: peps.python.org PEP 723: Inline script metadata: peps.python.org PyCharm: www.jetbrains.com JetBrains: www.jetbrains.com Visual Studio Code: code.visualstudio.com pandas: pandas.pydata.org PydanticAI: ai.pydantic.dev OpenAI API docs: platform.openai.com uv: docs.astral.sh Hatch: github.com PDM: pdm-project.org Poetry: python-poetry.org Project Jupyter: jupyter.org JupyterLite: jupyterlite.readthedocs.io PEP 690: Lazy Imports: peps.python.org PyTorch: pytorch.org Python concurrent.futures: docs.python.org Python Package Index (PyPI): pypi.org EuroPython: tickets.europython.eu TensorFlow: www.tensorflow.org Keras: keras.io PyCon US: us.pycon.org NumFOCUS: numfocus.org Python discussion forum (discuss.python.org): discuss.python.org Language Server Protocol: microsoft.github.io mypy: mypy-lang.org Pyright: github.com Pylance: marketplace.visualstudio.com Pyrefly: github.com ty: github.com Zuban: docs.zubanls.com Jedi: jedi.readthedocs.io GitHub: github.com PyOhio: www.pyohio.org Watch this episode on YouTube: youtube.com Episode #532 deep-dive: talkpython.fm/532 Episode transcripts: talkpython.fm Theme Song: Developer Rap
¿Qué hace realmente un usuario de Linux durante todo un año? En este episodio no teorizamos: auditamos. He analizado mi historial de comandos de 2025 y los datos no mienten.Desde el dominio absoluto de Rust hasta la sorprendente eficiencia de uv en Python, hoy te desvelo las 20 herramientas que han vertebrado mi flujo de trabajo. Hablamos de productividad real, de cómo Neovim ha desplazado definitivamente a mis antiguos editores y de por qué herramientas como just o yadm son las joyas ocultas que deberías estar usando ya.En este episodio descubrirás:El Stack de la Eficiencia: Mi top 20 analizado por categorías (Desarrollo, Sistema y Navegación).La transición a Rust: ¿Por qué cargo es el motor de mi día a día?Adiós a la fricción: Cómo herramientas modernas están sustituyendo a los comandos clásicos de toda la vida.Telemetría personal: El método para que tú también audites tu terminal.Si quieres llevar tu productividad en Linux al siguiente nivel y conocer qué software está marcando la diferencia en 2025, este episodio es tu hoja de ruta.
This is a recap of the top 10 posts on Hacker News on December 25, 2025. This podcast was generated by wondercraft.ai (00:30): We invited a man into our home at Christmas and he stayed with us for 45 yearsOriginal post: https://news.ycombinator.com/item?id=46383552&utm_source=wondercraft_ai(01:52): Ruby 4.0.0Original post: https://news.ycombinator.com/item?id=46382011&utm_source=wondercraft_ai(03:14): Alzheimer's disease can be reversed in animal models? StudyOriginal post: https://news.ycombinator.com/item?id=46384919&utm_source=wondercraft_ai(04:36): I sell onions on the Internet (2019)Original post: https://news.ycombinator.com/item?id=46385308&utm_source=wondercraft_ai(05:58): Maybe the default settings are too highOriginal post: https://news.ycombinator.com/item?id=46387657&utm_source=wondercraft_ai(07:20): Mattermost restricted access to old messages after 10000 limit is reachedOriginal post: https://news.ycombinator.com/item?id=46383675&utm_source=wondercraft_ai(08:42): Python 3.15's interpreter for Windows x86-64 should hopefully be 15% fasterOriginal post: https://news.ycombinator.com/item?id=46384167&utm_source=wondercraft_ai(10:04): Who Watches the Waymos? I do [video]Original post: https://news.ycombinator.com/item?id=46380758&utm_source=wondercraft_ai(11:26): Asahi Linux with Sway on the MacBook Air M2 (2024)Original post: https://news.ycombinator.com/item?id=46384565&utm_source=wondercraft_ai(12:48): Free Software Foundation receives historic private donationsOriginal post: https://news.ycombinator.com/item?id=46382134&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai
Чтобы научиться программировать и разбираться в тонкостях Python 3.12 записывайтесь на базовый курс Learn Python — https://clck.ru/3MuShF Ведущие – Григорий Петров и Михаил Корнеев Ссылки выпуска: Блог Коли Хитрова — https://t.me/nkhitrov_blog Канал Никиты Соболева — https://t.me/opensource_findings Курс Learn Python — https://learn.python.ru/advanced Канал Миши в Telegram — https://t.me/tricky_python Канал Moscow Python в Telegram — https://t.me/moscow_python Все выпуски — https://podcast.python.ru Митапы Moscow Python — https://moscowpython.ru Канал Moscow Python на Rutube — https://rutube.ru/channel/45885590/ Канал Moscow Python в VK — https://vk.com/moscowpythonconf Курс «Основы Python» от Learn Python — это отличный старт для новичков в программировании. За несколько уроков вы освоите базовый синтаксис, научитесь работать с данными и получите первый опыт для успешного старта карьеры в ИТ. Подробности: https://clck.ru/3MuShF
This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubCheck out more here:https://gotopia.tech/episodes/401Fabrizio Romano - Development Manager at Sohonet & Co-Author of "Learning Python Programming"Naomi Ceder - Python Instruction and Consulting & Author of "The Quick Python Book"RESOURCESFabriziohttps://x.com/gianchubhttps://github.com/gianchubhttps://www.linkedin.com/in/gianchubNaomihttps://bsky.app/profile/naomiceder.techhttps://github.com/ncederhttps://www.linkedin.com/in/naomicederhttps://www.naomiceder.techLinkhttps://adventofcode.comDESCRIPTIONNaomi Ceder interviews Fabrizio Romano, author of "Learning Python Programming" (now in its 4th edition). They discuss Fabrizio's decade-long journey as a Python programmer and book author, exploring how his perspectives have evolved across multiple editions.Key topics include the shift from GUI-focused content to command-line applications, the controversial introduction of typing in Python, the rise of AI in coding, and the importance of educating junior developers. Fabrizio emphasizes the balance between embracing new tools like AI while maintaining fundamental programming skills and the human element in software development.RECOMMENDED BOOKSFabrizio Romano & Heinrich Kruger • Learning Python Programming • https://amzn.to/4myLBItNaomi Ceder • The Quick Python Book • https://amzn.to/3zwdDOaLuciano Ramalho • Fluent Python • https://amzn.to/3oSw2jeDavid Beazley • Python Distilled (Developer's Library) • https://amzn.to/3QjNBEvAnna Skoulikari • Learning Git • https://amzn.to/4cSl8lzSy Brand • Building a Debugger • https://amzn.to/4cWWr84BlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!
Send us a textIn which we've talked about all the other Python projects, so why not?
This is a recap of the top 10 posts on Hacker News on December 23, 2025. This podcast was generated by wondercraft.ai (00:30): Inside CECOT – 60 Minutes [video]Original post: https://news.ycombinator.com/item?id=46361024&utm_source=wondercraft_ai(01:51): Fabrice Bellard Releases MicroQuickJSOriginal post: https://news.ycombinator.com/item?id=46367224&utm_source=wondercraft_ai(03:13): Meta is using the Linux scheduler designed for Valve's Steam Deck on its serversOriginal post: https://news.ycombinator.com/item?id=46366998&utm_source=wondercraft_ai(04:35): Instant database clones with PostgreSQL 18Original post: https://news.ycombinator.com/item?id=46363360&utm_source=wondercraft_ai(05:57): Ask HN: What are the best engineering blogs with real-world depth?Original post: https://news.ycombinator.com/item?id=46363921&utm_source=wondercraft_ai(07:18): We replaced H.264 streaming with JPEG screenshots (and it worked better)Original post: https://news.ycombinator.com/item?id=46367475&utm_source=wondercraft_ai(08:40): Snitch – A friendlier ss/netstatOriginal post: https://news.ycombinator.com/item?id=46361229&utm_source=wondercraft_ai(10:02): X-ray: a Python library for finding bad redactions in PDF documentsOriginal post: https://news.ycombinator.com/item?id=46369923&utm_source=wondercraft_ai(11:24): Show HN: CineCLI – Browse and torrent movies directly from your terminalOriginal post: https://news.ycombinator.com/item?id=46362655&utm_source=wondercraft_ai(12:45): 10 years bootstrapped: €6.5M revenue with a team of 13Original post: https://news.ycombinator.com/item?id=46363319&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai
The Datanation Podcast - Podcast for Data Engineers, Analysts and Scientists
Alex Merced (AlexMerced.com) discusses:– his thoughts on thriving in 2026– His use of Google’s Antigravity– His use of NotebookLM– Dremio’s AI tools (dremio.com)– More Check out Pangolin Catalog at PangolinCatalog.org
Dr Mark Palmeri is a professor at Duke University in the Biomedical Engineering (BME) field. He joins Chris to talk about using open tools (KiCad, ngspice, Zephyr, Jupyter notebooks, Python) to build educational resources and how he shares those courses with the world outside of Duke. He also walks through the Tympanometer project, built with Duke BME Design Fellows.
Topics covered in this episode: Has the cost of building software just dropped 90%? More on Deprecation Warnings How FOSS Won and Why It Matters Should I be looking for a GitHub alternative? Extras Joke Watch on YouTube About the show Sponsored by us! Support our work through: Our courses at Talk Python Training The Complete pytest Course Patreon Supporters Connect with the hosts Michael: @mkennedy@fosstodon.org / @mkennedy.codes (bsky) Brian: @brianokken@fosstodon.org / @brianokken.bsky.social Show: @pythonbytes@fosstodon.org / @pythonbytes.fm (bsky) Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Monday at 10am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. HEADS UP: We are taking next week off, happy holiday everyone. Michael #1: Has the cost of building software just dropped 90%? by Martin Alderson Agentic coding tools are collapsing “implementation time,” so the cost curve of shipping software may be shifting sharply Recent programming advancements haven't been that great of a true benefit: Cloud, TDD, microservices, complex frontends, Kubernetes, etc. Agentic AI's big savings are not just code generation, but coordination overhead reduction (fewer handoffs, fewer meetings, fewer blocks). Thinking, product clarity, and domain decisions stay hard, while typing and scaffolding get cheap. Is it the end of software dev? Not really, see Jevons paradox: when production gets cheaper, total demand can rise rather than spending simply falling. (Historically: the efficiency of coal use led to the increased consumption of coal) Pushes back on “only good for greenfield” by arguing agents also help with legacy code comprehension and bug-fixing. I 100% agree. #Legacy code for the win. Brian #2: More on Deprecation Warnings How are people ignoring them? yep, it's right in the Python docs: -W ignore::DeprecationWarning Don't do that! Perhaps the docs should give the example of emitting them only once -W once::::DeprecationWarning See also -X dev mode , which sets -W default and some other runtime checks Don't use warn, use the @warnings.deprecated decorator instead Thanks John Hagen for pointing this out Emits a warning It's understood by type checkers, so editors visually warn you You can pass in your own custom UserWarning with category mypy also has a command line option and setting for this --enable-error-code deprecated or in [tool.mypy] enable_error_code = ["deprecated"] My recommendation Use @deprecated with your own custom warning and test with pytest -W error Michael #3: How FOSS Won and Why It Matters by Thomas Depierre Companies are not cheap, companies optimize cost control. They do this by making purchasing slow and painful. FOSS is/was a major unlock hack to skip procurement, legal, etc. Example is months to start using a paid “Add to calendar” widget! It “works both ways”: the same bypass lowers the barrier for maintainers too, no need for a legal entity, lawyers, liability insurance, or sales motion. Proposals that “fix FOSS” by reintroducing supply-chain style controls (he name-checks SBOMs and mandated processes) risk being rejected or gamed, because they restore the very friction FOSS sidesteps. Brian #4: Should I be looking for a GitHub alternative? Pricing changes for GitHub Actions The self-hosted runner pricing change caused a kerfuffle. It's has been postponed But… if you were to look around, maybe pay attention to These 4 GitHub alternatives are just as good—or better Codeburg, BitBucket, GitLab, Gitea And a new-ish entry, Tangled Extras Brian: End of year sale for The Complete pytest Course Use code XMAS2025 for 50% off before Dec 31 Writing work on Lean TDD book on hold for holidays Will pick up again in January Michael: PyCharm has better Ruff support now out of the box, via Daniel Molnar This is from the release notes of 2025.3: "PyCharm 2025.3 expands its LSP integration with support for Ruff, ty, Pyright, and Pyrefly.” If you check out the LSP section it will land you on this page and you can go to Ruff. The Ruff doc site was also updated. Previously it was only available external tools and a third party plugin, this feels like a big step. Fun quote I saw on ExTwitter: May your bug tracker be forever empty. Joke: Try/Catch/Stack Overflow Create a super annoying linkedin profile - From Tim Kellogg, submitted by archtoad
Building a Fiction Editing Pipeline with Regex and Python — Part 1 by Eddie Tonkoi Support the Show CCATP #826 — Adam Engst on The Phone App in iOS 26 Transcript of NC_2025_12_25 Join the Conversation: allison@podfeet.com podfeet.com/slack Support the Show: Patreon Donation Apple Pay or Credit Card one-time donation PayPal one-time donation Podfeet Podcasts Mugs at Zazzle NosillaCast 20th Anniversary Shirts Referral Links: Setapp - 1 month free for you and me PETLIBRO - 30% off for you and me Parallels Toolbox - 3 months free for you and me Learn through MacSparky Field Guides - 15% off for you and me Backblaze - One free month for me and you Eufy - $40 for me if you spend $200. Sadly nothing in it for you. PIA VPN - One month added to Paid Accounts for both of us CleanShot X - Earns me $25%, sorry nothing in it for you but my gratitude
In this episode, Conor chats with Kevlin Henney about the past, present and future of programming languages and with Damian Maclennan about YOW! 2025!Link to Episode 265 on WebsiteDiscuss this episode, leave a comment, or ask a question (on GitHub)SocialsADSP: The Podcast: TwitterConor Hoekstra: LinkTree / BioAbout the Guests:Kevlin Henney is an independent consultant, speaker, writer and trainer. His software development interests are in programming, practice and people. He has been a columnist for various magazines and websites. He is the co-author of A Pattern Language for Distributed Computing and On Patterns and Pattern Languages, two volumes in the Pattern-Oriented Software Architecture series, and editor of 97 Things Every Programmer Should Know and co-editor of 97 Things Every Java Programmer Should Know.Damian Maclennan is a technologist, software architect, trainer, developer, cyclist, and musician in Brisbane, Australia. With over twenty five years experience building software and leading teams across many industries he has worked as a developer, software architect, consultant, troubleshooter, trainer and educator, and senior leader. Damian is the Technical Director of YOW! Conferences. Full bio here.Show NotesDate Recorded: 2025-12-11Date Released: 2025-12-19YOW Conferences!ADSP Episode 190: C++, Python and More with Kevlin Henney97 Things Every Programmer Should KnowThe Past, Present and Future of Programming Languages - Kevlin Henney - ACCU 2025The Past, Present & Future of Programming Languages • Kevlin Henney • GOTO 2024TIOBE Language RankingsRedMonk Language RankingsProgramming Language RankingsContext Free YouTubeYOW! 2025 - Beyond Sonic Pi: Tau5 and the Art of Coding with AI - Sam AaronYOW! 2025 - Conceptualisation - Michael FeathersIntro Song InfoMiss You by Sarah Jansen https://soundcloud.com/sarahjansenmusicCreative Commons — Attribution 3.0 Unported — CC BY 3.0Free Download / Stream: http://bit.ly/l-miss-youMusic promoted by Audio Library https://youtu.be/iYYxnasvfx8
Talk Python To Me - Python conversations for passionate developers
Have you ever thought about getting your small product into production, but are worried about the cost of the big cloud providers? Or maybe you think your current cloud service is over-architected and costing you too much? Well, in this episode, we interview Michael Kennedy, author of "Talk Python in Production," a new book that guides you through deploying web apps at scale with right-sized engineering. Episode sponsors Seer: AI Debugging, Code TALKPYTHON Agntcy Talk Python Courses Links from the show Christopher Trudeau - guest host: www.linkedin.com Michael's personal site: mkennedy.codes Talk Python in Production Book: talkpython.fm glances: github.com btop: github.com Uptimekuma: uptimekuma.org Coolify: coolify.io Talk Python Blog: talkpython.fm Hetzner (€20 credit with link): hetzner.cloud OpalStack: www.opalstack.com Bunny.net CDN: bunny.net Galleries from the book: github.com Pandoc: pandoc.org Docker: www.docker.com Watch this episode on YouTube: youtube.com Episode #531 deep-dive: talkpython.fm/531 Episode transcripts: talkpython.fm Theme Song: Developer Rap
Today Eric Chou dives deep into network automation and operational simplicity with guest Hardik Ajmera, VP of Product Management at Extreme Networks. In this sponsored episode, they talk about the ‘network fabric', Extreme Platform ONE, and, of course, what's next with AI in the world of enterprise networking. Hardik also shares how customers in complex... Read more »
Today Eric Chou dives deep into network automation and operational simplicity with guest Hardik Ajmera, VP of Product Management at Extreme Networks. In this sponsored episode, they talk about the ‘network fabric', Extreme Platform ONE, and, of course, what's next with AI in the world of enterprise networking. Hardik also shares how customers in complex... Read more »
Gabe Kunda (Marvel Rivals, Apex Legends) and Natasha Rothwell (The White Lotus, Insecure) co-star in a Ugandan legend about friendship, rivalry, and making music. Sign up for our monthly newsletter, "The Lion's Roar", here.
Topics covered in this episode: Deprecations via warnings docs PyAtlas: interactive map of the top 10,000 Python packages on PyPI. Buckaroo Extras Joke Watch on YouTube About the show Connect with the hosts Michael: @mkennedy@fosstodon.org / @mkennedy.codes (bsky) Brian: @brianokken@fosstodon.org / @brianokken.bsky.social Show: @pythonbytes@fosstodon.org / @pythonbytes.fm (bsky) Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Monday at 10am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Brian #1: Deprecations via warnings Deprecations via warnings don't work for Python libraries Seth Larson How to encourage developers to fix Python warnings for deprecated features Ines Panker Michael #2: docs A collaborative note taking, wiki and documentation platform that scales. Built with Django and React. Made for self hosting Docs is the result of a joint effort led by the French
In this episode of the HuntFishTravel Podcast, I sit down with Amy Siewe, better known as The Python Huntress. Amy is a professional python hunter working on the front lines of conservation in Florida, helping remove one of the most destructive invasive species in North America. We talk about how she went from real estate broker to full-time python hunter, what it's actually like to hunt massive snakes in the wild, and why this work is so critical to protecting native wildlife in the Everglades. We dive deep into how Burmese pythons ended up in Florida in the first place, the impact they've had on native mammals and ecosystems, what a real python hunt looks like, from spotlighting roads at night to catching snakes by hand, the largest python Amy has ever caught and a wild story to go with it, and how python hunting ties directly into scientific research and conservation. This episode is fascinating, intense, occasionally jaw-dropping (I probably said "bananas" way too many times to count), and deeply rooted in responsible conservation. Amy's respect for wildlife and the Everglades comes through loud and clear and I walked away with a whole new understanding of just how serious the python problem really is. Whether you're a hunter, angler, conservationist, or just someone who loves wild stories from the field, this is an episode you don't want to miss. Learn more or book a hunt: pythonhuntress.com Follow Amy's adventures: @thepythonhuntress on Instagram and @pythonhuntress on Facebook. Timestamps: 00:00 – 01:24 – Opening intro & setting the Everglades scene 01:24 – 02:37 – Meet Amy Siewe, The Python Huntress 02:37 – 04:05 – How Amy became a professional python hunter 04:05 – 05:48 – From thrill-seeking to conservation mission 05:48 – 07:16 – How Burmese pythons invaded Florida 07:16 – 08:47 – Population explosion & lack of predators 08:47 – 10:22 – How big pythons get (and how dangerous they could be) 10:22 – 12:18 – What pythons eat & ecosystem collapse 12:18 – 14:17 – Why the Everglades are the perfect python habitat 14:17 – 15:55 – How python hunts actually work 15:55 – 16:18 – Catching pythons by hand 16:18 – 17:30 – Spotting snakes at night 17:30 – 24:46 – The 17-foot, 110-pound python story 24:46 – 26:39 – Why live capture is necessary 26:39 – 29:07 – Research, data, and working with biologists 29:07 – 30:44 – Hair-raising moments in the field 30:44 – 31:39 – Licensing, legality, and invasive species rules 31:39 – 33:29 – Ethics, conservation, and respecting wildlife 33:29 – 35:25 – Booking a hunt & following Amy online 35:25 – 36:03 – Final thoughts & wrap-up
Send us a textWe trace a journey from a teenage online threat to security engineering at global scale, exploring how deep fundamentals and distributed thinking shape reliable defenses. Along the way, we unpack certifications, teaching at scale, and building a practical path for learners worldwide.• curiosity-driven path from fear to purpose• foundations before security: systems then networks• depth of concepts vs surface knowledge• thinking at scale with distributed systems• threat modeling as a constant that endures• learning the why behind legacy architectures• community building through a book and courses• coding confidence for security practitioners• practical framework for choosing certifications• direction over collecting badges• reflecting on progress and resetting goals• links to connect and learn moreUse the code security50 to get 50% off the upcoming cybersecurity bootcamp at learn.thecyberinstructor.comPodMatchPodMatch Automatically Matches Ideal Podcast Guests and Hosts For InterviewsSupport the showFollow the Podcast on Social Media! Tesla Referral Code: https://ts.la/joseph675128 YouTube: https://www.youtube.com/@securityunfilteredpodcast Instagram: https://www.instagram.com/secunfpodcast/Twitter: https://twitter.com/SecUnfPodcast Affiliates➡️ OffGrid Faraday Bags: https://offgrid.co/?ref=gabzvajh➡️ OffGrid Coupon Code: JOE➡️ Unplugged Phone: https://unplugged.com/Unplugged's UP Phone - The performance you expect, with the privacy you deserve. Meet the alternative. Use Code UNFILTERED at checkout*See terms and conditions at affiliated webpages. Offers are subject to change. These are affiliated/paid promotions.
We're sending songs in your general direction with two implacable knights of the musical Round Table--Eric Idle and John Du Prez--the songwriters of Spamalot in our studio; plus numerous other Python musical treats.
Julian Sequeira from PyBites joins Sean and Kelly to share their top holiday gift picks for coders, makers, and educators. This episode features 15+ gift ideas ranging from budget-friendly maker tools to classroom robots—plus book recommendations, coding platforms, and a few surprises. Show Notes Wins of the Week Julian: Staying focused on "the one thing" at PyBites, plus 3D printing a custom cappuccino stencil for his local café Kelly: Surviving a muddy, clay-covered hill in North Carolina while on vacation Sean: Designing and 3D printing a custom bracket for his screen door using Fusion 360 Holiday Gift Ideas Julian's Picks Hoverboard with Go-Kart Attachment (~$299 AUD) - Two-wheeled self-balancing boards that can convert to a go-kart with a third wheel attachment. Available at Hoveroo (https://hoveroo.com.au) in Australia. Secret Coders Book Series (~$10-20 USD each) - A six-book graphic novel series that wraps coding puzzles and concepts into mystery stories. Recommended by Faye Shaw from the Boston PyLadies community. Great for ages 8-15. 3D Printer (~$200-300 USD) - Entry-level printers like the Bambu Lab A1 Mini or Elegoo Neptune 4 Pro have dropped significantly in price. Look for auto bed leveling as a key feature. Duolingo Chess (~$13/month with subscription) - A new addition to Duolingo that teaches chess tactics, strategy, and formal terminology through structured lessons. Great for building problem-solving skills. Classic Video Games (Zelda, Pokémon) - Story-driven games that build resilience and problem-solving skills, as an alternative to dopamine-heavy platforms like Roblox. Kelly's Picks Soccer Bot (~$59.99) - An indoor soccer training robot that challenges footwork skills. Works best on hard floors. "The Worlds I See" by Dr. Fei-Fei Li - Memoir of the computer scientist behind ImageNet and modern image recognition, covering her immigrant journey and rise in AI. A must-read for anyone interested in AI. LEGO Retro Radio Building Set (~$99) - A 1970s-style radio that you build, then insert your phone to play music. Features working dials that create authentic radio crackle sounds. Spydroid Loco Hex Robot (classroom investment) - A large spider-shaped robot that codes in Python and block programming. Features LIDAR and AI-based mapping. Seen at ISTE. Richtie Mini from Hugging Face ($299-$449) - An adorable AI desktop companion robot with onboard models. Two versions: one that connects to your computer and one that's self-contained. Sean's Picks LED Pucks (LED 001 Kit) (~$6-13) - Small USB-powered LED discs perfect for 3D printed projects like planet lamps. Available from Bambu Labs or Amazon. RGB versions include remote controls. Daily Desk Calendar (~$15-20) - A throwback gift that provides daily doses of humor, trivia, or inspiration. Suggestions include The Far Side, "They Can Talk," or "How to Win Friends and Influence People." PyBites Coding Platform (subscription) - Bite-sized Python challenges for sharpening coding skills. Great for teachers, students, and professionals looking for practical coding practice. Digital Calipers (~$40-50) - USB-rechargeable precision measuring tools essential for 3D printing and maker projects. Great for teaching geometry and measurement concepts. Deburring Tool (~$10) - A small tool with a curved swiveling blade for cleaning up 3D prints. A quality-of-life improvement for any maker's toolkit. Links Mentioned PyBites (https://pybit.es) - Python coaching and coding challenges Hoveroo (https://hoveroo.com.au) - Hoverboards (Australia) Bambu Lab (https://bambulab.com) - 3D printers and LED pucks Printables (https://www.printables.com) - 3D printing models MakerWorld (https://makerworld.com) - 3D printing models Hugging Face Richtie Mini (https://huggingface.co) - AI companion robot Duolingo (https://duolingo.com) - Language learning app with chess Secret Coders book series - Available on Amazon "The Worlds I See" by Dr. Fei-Fei Li - Available at bookstores Upcoming Events PyCon US 2026 - Long Beach, California Education Summit - Proposals open after the holidays, deadline around March/April Submit proposals when the website opens! Special Guest: Julian Sequeira.
JUST A FLESH WOUND!! Monty Python and the Holy Grail Full Movie Reaction Watch Along: / thereelrejects Start your online business with a $1 per-month trial when you visit https://www.shopify.com/rejects! Monty Python's The Life of Brian (1979) Movie Reaction: • MONTY PYTHON'S LIFE OF BRIAN (1979) MOVIE ... Gift Someone (Or Yourself) A Stranger Things RR Tee! https://shorturl.at/hekk2 Aaron Alexander & Andrew Gordon dive into the legendary British comedy that redefined absurdist humor and became one of the most quoted films of all time!! Join us on our Monty Python & the Holy Grail Reaction, Breakdown, Commentary, Analysis & Spoiler Review! Andrew Gordon (Cinepals) & Aaron Alexander (Silhouettes of Scarlet) react to Monty Python and the Holy Grail (1975), the legendary sketch-comedy satire written and performed by the Monty Python troupe and directed by Terry Gilliam & Terry Jones. A wildly absurd reimagining of Arthurian legend, the film follows King Arthur on a quest from God to find the Holy Grail — a mission constantly derailed by anachronisms, low-budget chaos, and some of the most quoted jokes in comedy history. Graham Chapman (Life of Brian, Monty Python's Flying Circus) stars as the straight-faced King Arthur, valiantly leading his Knights of the Round Table while pretending everything around him makes sense. The ensemble brilliance comes from Python regulars John Cleese (A Fish Called Wanda, Fawlty Towers) as the endlessly shouty Sir Lancelot (and the infamous Black Knight), Eric Idle (Life of Brian, Shrek) as the sing-songy Sir Robin, Terry Jones (Life of Brian, Meaning of Life) as Sir Bedevere, and Michael Palin (Brazil, A Fish Called Wanda) as Sir Galahad, along with dozens of other roles played interchangeably by the troupe. Follow Aaron On Instagram: https://www.instagram.com/therealaaronalexander/?hl=en Follow Andrew Gordon on Socials: YouTube: https://www.youtube.com/@MovieSource Instagram: https://www.instagram.com/agor711/?hl=en Twitter: https://twitter.com/Agor711 Intense Suspense by Audionautix is licensed under a Creative Commons Attribution 4.0 license. https://creativecommons.org/licenses/... Support The Channel By Getting Some REEL REJECTS Apparel! https://www.rejectnationshop.com/ Follow Us On Socials: Instagram: https://www.instagram.com/reelrejects/ Tik-Tok: https://www.tiktok.com/@reelrejects?lang=en Twitter: https://x.com/reelrejects Facebook: https://www.facebook.com/TheReelRejects/ Music Used In Ad: Hat the Jazz by Twin Musicom is licensed under a Creative Commons Attribution 4.0 license. https://creativecommons.org/licenses/by/4.0/ Happy Alley by Kevin MacLeod is licensed under a Creative Commons Attribution 4.0 license. https://creativecommons.org/licenses/... POWERED BY @GFUEL Visit https://gfuel.ly/3wD5Ygo and use code REJECTNATION for 20% off select tubs!! Head Editor: https://www.instagram.com/praperhq/?hl=en Co-Editor: Greg Alba Co-Editor: John Humphrey Music In Video: Airport Lounge - Disco Ultralounge by Kevin MacLeod is licensed under a Creative Commons Attribution 4.0 license. https://creativecommons.org/licenses/by/4.0/ Ask Us A QUESTION On CAMEO: https://www.cameo.com/thereelrejects Follow TheReelRejects On FACEBOOK, TWITTER, & INSTAGRAM: FB: https://www.facebook.com/TheReelRejects/ INSTAGRAM: https://www.instagram.com/reelrejects/ TWITTER: https://twitter.com/thereelrejects Follow GREG ON INSTAGRAM & TWITTER: INSTAGRAM: https://www.instagram.com/thegregalba/ TWITTER: https://twitter.com/thegregalba Learn more about your ad choices. Visit megaphone.fm/adchoices
Talk Python To Me - Python conversations for passionate developers
For years, building interactive widgets in Python notebooks meant wrestling with toolchains, platform quirks, and a mountain of JavaScript machinery. Most developers took one look and backed away slowly. Trevor Manz decided that barrier did not need to exist. His idea was simple: give Python users just enough JavaScript to unlock the web's interactivity, without dragging along the rest of the web ecosystem. That idea became anywidget, and it is quickly becoming the quiet connective tissue of modern interactive computing. Today we dig into how it works, why it has taken off, and how it might change the way we explore data. Episode sponsors Seer: AI Debugging, Code TALKPYTHON PyCharm, code STRONGER PYTHON Talk Python Courses Links from the show Trevor on GitHub: github.com anywidget GitHub: github.com Trevor's SciPy 2024 Talk: www.youtube.com Marimo GitHub: github.com Myst (Markdown docs): mystmd.org Altair: altair-viz.github.io DuckDB: duckdb.org Mosaic: uwdata.github.io ipywidgets: ipywidgets.readthedocs.io Tension between Web and Data Sci Graphic: blobs.talkpython.fm Quak: github.com Walk through building a widget: anywidget.dev Widget Gallery: anywidget.dev Video: How do I anywidget?: www.youtube.com PyCharm + PSF Fundraiser: pycharm-psf-2025 code STRONGER PYTHON Watch this episode on YouTube: youtube.com Episode #530 deep-dive: talkpython.fm/530 Episode transcripts: talkpython.fm Theme Song: Developer Rap
BONUS: Swimming in Tech Debt — Practical Techniques to Keep Your Team from Drowning in Its Codebase In this fascinating conversation, veteran software engineer and author Lou Franco shares hard-won lessons from decades at startups, Trello, and Atlassian. We explore his book "Swimming in Tech Debt," diving deep into the 8 Questions framework for evaluating tech debt decisions, personal practices that compound over time, team-level strategies for systematic improvement, and leadership approaches that balance velocity with sustainability. Lou reveals why tech debt is often the result of success, how to navigate the spectrum between ignoring debt and rewriting too much, and practical techniques individuals, teams, and leaders can use starting today. The Exit Interview That Changed Everything "We didn't go slower by paying tech debt. We went actually faster, because we were constantly in that code, and now we didn't have to run into problems." — Lou Franco Lou's understanding of tech debt crystallized during an exit interview at Atalasoft, a small startup where he'd spent years. An engineer leaving the company confronted him: "You guys don't care about tech debt." Lou had been focused on shipping features, believing that paying tech debt would slow them down. But this engineer told a different story — when they finally fixed their terrible build and installation system, they actually sped up. They were constantly touching that code, and removing the friction made everything easier. This moment revealed a fundamental truth: tech debt isn't just about code quality or engineering pride. It's about velocity, momentum, and the ability to move fast sustainably. Lou carried this lesson through his career at Trello (where he learned the dangers of rewriting too much) and Atlassian (where he saw enterprise-scale tech debt management). These experiences became the foundation for "Swimming in Tech Debt." Tech Debt Is the Result of Success "Tech debt is often the result of success. Unsuccessful projects don't have tech debt." — Lou Franco This reframes the entire conversation about tech debt. Failed products don't accumulate debt — they disappear before it matters. Tech debt emerges when your code survives long enough to outlive its original assumptions, when your user base grows beyond initial expectations, when your team scales faster than your architecture anticipated. At Atalasoft, they built for 10 users and got 100. At Trello, mobile usage exploded beyond their web-first assumptions. Success creates tech debt by changing the context in which code operates. This means tech debt conversations should happen at different intensities depending on where you are in the product lifecycle. Early startups pursuing product-market fit should minimize tech debt investments — move fast, learn, potentially throw away the code. Growth-stage companies need balanced approaches. Mature products benefit significantly from tech debt investments because operational efficiency compounds over years. Understanding this lifecycle perspective helps teams make appropriate decisions rather than applying one-size-fits-all rules. The 8 Questions Framework for Tech Debt Decisions "Those 8 questions guide you to what you should do. If it's risky, has regressions, and you don't even know if it's gonna work, this is when you're gonna do a project spike." — Lou Franco Lou introduces a systematic framework for evaluating whether to pay tech debt, inspired by Bob Moesta's push-pull forces from product management. The 8 questions create a complete picture: Visibility — Will people outside the team understand what we're doing? Alignment — Does this match our engineering values and target architecture? Resistance — How hard is this code to work with right now? Volatility — How often do we touch this code? Regression Risk — What's the chance we'll introduce new problems? Project Size — How big is this to fix? Estimate Risk — How uncertain are we about the effort required? Outcome Uncertainty — How confident are we the fix will actually improve things? High volatility and high resistance with low regression risk? Pay the debt now. High regression risk with no tests? Write tests first, then reassess. Uncertain outcomes on a big project? Do a spike or proof of concept. The framework prevents both extremes — ignoring costly debt and undertaking risky rewrites without proper preparation. Personal Practices That Compound Daily "When I sit down at my desk, the first thing I do is I pay a little tech debt. I'm looking at code, I'm about to change it, do I even understand it? Am I having some kind of resistance to it? Put in a little helpful comment, maybe a little refactoring." — Lou Franco Lou shares personal habits that create compounding improvements over time. Start each coding session by paying a small amount of tech debt in the area you're about to work — add a clarifying comment, extract a confusing variable, improve a function name. This warms you up, reduces friction for your actual work, and leaves the code slightly better than you found it. The clean-as-you-go philosophy means tech debt never accumulates faster than you can manage it. But Lou's most powerful practice comes at the end of each session: mutation testing by hand. Before finishing for the day, deliberately break something — change a plus to minus, a less-than to less-than-or-equal. See if tests catch it. Often they don't, revealing gaps in test coverage. The key insight: don't fix it immediately. Leave that failing test as the bridge to tomorrow's coding session. It connects today's momentum to tomorrow's work, ensuring you always start with context and purpose rather than cold-starting each day. Mutation Testing: Breaking Things on Purpose "Before I'm done working on a coding session, I break something on purpose. I'll change a plus to a minus, a less than to a less than equals, and see if tests break. A lot of times tests don't break. Now you've found a problem in your test." — Lou Franco Manual mutation testing — deliberately breaking code to verify tests catch the break — reveals a critical gap in most test suites. You can have 100% code coverage and still have untested behavior. A line of code that's executed during tests isn't necessarily tested — the test might not actually verify what that line does. By changing operators, flipping booleans, or altering constants, you discover whether your tests protect against actual logic errors or just exercise code paths. Lou recommends doing this manually as part of your daily practice, but automated tools exist for systematic discovery: Stryker (for JavaScript, C#, Scala) and MutMut (for Python) can mutate your entire codebase and report which mutations survive uncaught. This isn't just about test quality — it's about understanding what your code actually does and building confidence that changes won't introduce subtle bugs. Team-Level Practices: Budgets, Backlogs, and Target Architecture "Create a target architecture document — where would we be if we started over today? Every PR is an opportunity to move slightly toward that target." — Lou Franco At the team level, Lou advocates for three interconnected practices. First, create a target architecture document that describes where you'd be if starting fresh today — not a detailed design, but architectural patterns, technology choices, and structural principles that represent current best practices. This isn't a rewrite plan; it's a North Star. Every pull request becomes an opportunity to move incrementally toward that target when touching relevant code. Second, establish a budget split between PM-led feature work and engineering-led tech debt work — perhaps 80/20 or whatever ratio fits your product lifecycle stage. This creates predictable capacity for tech debt without requiring constant negotiation. Third, hold quarterly tech debt backlog meetings separate from sprint planning. Treat this backlog like PMs treat product discovery — explore options, estimate impacts, prioritize based on the 8 Questions framework. Some items fit in sprints; others require dedicated engineers for a quarter or two. This systematic approach prevents tech debt from being perpetually deprioritized while avoiding the opposite extreme of engineers disappearing into six-month "improvement" projects with no visible progress. The Atlassian Five-Alarm Fire "The Atlassian CTO's 'five-alarm fire' — stopping all feature development to focus on reliability. I reduced sync errors by 75% during that initiative." — Lou Franco Lou shares a powerful example of leadership-driven tech debt management at scale. The Atlassian CTO called a "five-alarm fire" — halting all feature development across the company to focus exclusively on reliability and tech debt. This wasn't panic; it was strategic recognition that accumulated debt threatened the business. Lou worked on reducing sync errors, achieving a 75% reduction during this focused period. The initiative demonstrated several leadership principles: willingness to make hard calls that stop revenue-generating feature work, clear communication of why reliability matters strategically, trust that teams will use the time wisely, and commitment to see it through despite pressure to resume features. This level of intervention is rare and shouldn't be frequent, but it shows what's possible when leadership truly prioritizes tech debt. More commonly, leaders should express product lifecycle constraints (startup urgency vs. mature product stability), give teams autonomy to find appropriate projects within those constraints, and require accountability through visible metrics and dashboards that show progress. The Rewrite Trap: Why Big Rewrites Usually Fail "A system that took 10 years to write has implicit knowledge that can't be replicated in 6 months. I'm mostly gonna advocate for piecemeal migrations along the way, reducing the size of the problem over time." — Lou Franco Lou lived through Trello's iOS navigation rewrite — a classic example of throwing away working code to start fresh, only to discover all the edge cases, implicit behaviors, and user expectations baked into the "old" system. A codebase that evolved over several years contains implicit knowledge — user workflows, edge case handling, performance optimizations, and subtle behaviors that users rely on even if they never explicitly requested them. Attempting to rewrite this in six months inevitably misses critical details. Lou strongly advocates for piecemeal migrations instead. The Trello "Decaffeinate Project" exemplifies this approach — migrating from CoffeeScript to TypeScript incrementally, with public dashboards showing the percentage remaining, interoperable technologies allowing gradual transition, and the ability to pause or reverse if needed. Keep both systems running in parallel during migrations. Use runtime observability to verify new code behaves identically to old code. Reduce the problem size steadily over months rather than attempting big-bang replacements. The only exception: sometimes keeping parallel systems requires scaffolding that creates its own complexity, so evaluate whether piecemeal migration is actually simpler or if you're better off living with the current system. Making Tech Debt Visible Through Dashboards "Put up a dashboard, showing it happen. Make invisible internal improvements visible through metrics engineering leadership understands." — Lou Franco One of tech debt's biggest challenges is invisibility — non-technical stakeholders can't see the improvement from refactoring or test coverage. Lou learned to make tech debt work visible through dashboards and metrics. The Decaffeinate Project tracked percentage of CoffeeScript files remaining, providing a clear progress indicator anyone could understand. When reducing sync errors, Lou created dashboards showing error rates declining over time. These visualizations serve multiple purposes: they demonstrate value to leadership, create accountability for engineering teams, build momentum as progress becomes visible, and help teams celebrate wins that would otherwise go unnoticed. The key is choosing metrics that matter to the business — error rates, page load times, deployment frequency, mean time to recovery — rather than pure code quality metrics like cyclomatic complexity that don't translate outside engineering. Connect tech debt work to customer experience, reliability, or developer productivity in ways leadership can see and value. Onboarding as a Tech Debt Opportunity "Unit testing is a really great way to learn a system. It's like an executable specification that's helping you prove that you understand the system." — Lou Franco Lou identifies onboarding as an underutilized opportunity for tech debt reduction. When new engineers join, they need to learn the codebase. Rather than just reading code or shadowing, Lou suggests having them write unit tests in areas they're learning. This serves dual purposes: tests are executable specifications that prove understanding of system behavior, and they create safety nets in areas that likely lack coverage (otherwise, why would new engineers be confused by the code?). The new engineer gets hands-on learning, the team gets better test coverage, and everyone wins. This practice also surfaces confusing code — if new engineers struggle to understand what to test, that's a signal the code needs clarifying comments, better naming, or refactoring. Make onboarding a systematic tech debt reduction opportunity rather than passive knowledge transfer. Leadership's Role: Constraints, Autonomy, and Accountability "Leadership needs to express the constraints. Tell the team what you're feeling about tech debt at a high level, and what you think generally is the appropriate amount of time to be spent on it. Then give them autonomy." — Lou Franco Lou distills leadership's role in tech debt management to three elements. First, express constraints — communicate where you believe the product is in its lifecycle (early startup, rapid growth, mature cash cow) and what that means for tech debt tolerance. Are we pursuing product-market fit where code might be thrown away? Are we scaling a proven product where reliability matters? Are we maintaining a stable system where operational efficiency pays dividends? These constraints help teams make appropriate trade-offs. Second, give autonomy — once constraints are clear, trust teams to identify specific tech debt projects that fit those constraints. Engineers understand the codebase's pain points better than leaders do. Third, require accountability — teams must make their work visible through dashboards, metrics, and regular updates. Autonomy without accountability becomes invisible engineering projects that might not deliver value. Accountability without autonomy becomes micromanagement that wastes engineering judgment. The balance creates space for teams to make smart decisions while keeping leadership informed and confident in the investment. AI and the Future of Tech Debt "I really do AI-assisted software engineering. And by that, I mean I 100% review every single line of that code. I write the tests, and all the code is as I would have written it, it's just a lot faster. Developers are still responsible for it. Read the code." — Lou Franco Lou has a chapter about AI in his book, addressing the elephant in the room: will AI-generated code create massive tech debt? His answer is nuanced. AI can accelerate development tremendously if used correctly — Lou uses it extensively but reviews every single line, writes all tests himself, and ensures the code matches what he would have written manually. The problem emerges with "vibe coders" — non-developers using AI to generate code they don't understand, creating unmaintainable messes that become someone else's problem. Developers remain responsible for all code, regardless of how it's generated. This means you must read and understand AI-generated code, not blindly accept it. Lou also raises supply chain security concerns — dependencies can contain malicious code, and AI might introduce vulnerabilities developers miss. His recommendation: stay six months behind on dependency updates, let others discover the problems first, and consider separate sandboxed development machines to limit security exposure. AI is a powerful tool, but it doesn't eliminate the need for engineering judgment, testing discipline, or code review practices. The Style Guide Beyond Formatting "Have a style guide that goes beyond formatting to include target architecture. This is the kind of code we want to write going forward." — Lou Franco Lou advocates for style guides that extend beyond tabs-versus-spaces formatting rules to include architectural guidance. Document patterns you want to move toward: how should components be structured, what state management approaches do we prefer, how should we handle errors, what testing patterns should we follow? This creates a shared understanding of the target architecture without requiring a massive design document. When reviewing pull requests, teams can reference the style guide to explain why certain approaches align with where the codebase is headed versus perpetuating old patterns. This makes tech debt conversations less personal and more objective — it's not about criticizing someone's code, it's about aligning with team standards and strategic direction. The style guide becomes a living document that evolves as the team learns and technology changes, capturing collective wisdom about what good code looks like in your specific context. Recommended Resources Some of the resources mentioned in this episode include: Steve Blank's Four Steps To Epiphany The podcast episode with Bernie Maloney where we discuss the critical difference between "enterprise" and "startup". And Geoffrey Moore's Crossing the Chasm, and Dealing with Darwin. About Lou Franco Lou Franco is a veteran software engineer and author of Swimming in Tech Debt. With decades of experience at startups, as well as Trello, and Atlassian, he's seen both sides of debt—as coder and leader. Today, he advises teams on engineering practices, helping them turn messy codebases into momentum. You can link with Lou Franco on LinkedIn and learn more at LouFranco.com.
People often ask what I'm actually building with AI all day. In this episode, I break down the 6 active projects I'm coding right now to automate my work and save money:The QuickBooks Killer: Replacing a $30/month subscription with a custom Python & Plaid script for automated tax reporting.Content Agent: Automatically converting podcast audio into a written Substack newsletter.Voice-First Trading Journal: A system to log trading results and tax liabilities verbally into a secure database.Global Earnings Tracker: Monitoring earnings revisions across US and global markets.The Buffett Scan: An automated scanner finding stocks that meet Warren Buffett's investing criteria.Yutori Scouts: Using a new navigator API to dig up better market intel than Google News.
The python spirit is suffocating believers' prayer lives, prophetic voices, and even their physical health—but you don't have to live bound. In this powerful prophetic spiritual warfare teaching, Kathy DeGraw exposes python attacks and leads you into supernatural deliverance and freedom in Christ.. Purchase Kathy's book Healed at Last – Overcome Sickness to Receive your Physical Healing on Amazon https://a.co/d/6a6mt8w or at: https://www.kathydegrawministries.org/healed-at-last/ Purchase Anointing Oil with a prayer cloth that Kathy has personally mixed and prayed over on Kathy's Website or Amazon. Order anointing oil by Kathy on Amazon look for her brand here https://amzn.to/3PC6l3R or Kathy DeGraw Ministries https://www.kathydegrawministries.org/product-category/oils/ Training, Mentorship and Deliverance! Personal coaching, deliverance, e-courses, training for ministry, and mentorships! https://www.kathydegrawministries.org/training/# In this prophetic spiritual warfare message, Kathy DeGraw exposes the python spirit—the demonic force that comes to constrict your breath, silence your prophetic voice, and keep you spiritually stagnant. Drawing from Acts 16 and years of deliverance ministry, Kathy shows how python partners with witchcraft, infirmity, respiratory issues, and even stroke-like symptoms to choke out your destiny and keep you from prayer, worship, and the Word. If you've felt constantly tired, prayerless, unable to read your Bible, or like your spiritual hunger has dried up, this may be more than "laziness." Kathy reveals how past occult involvement, Halloween participation, horoscopes, counterfeit prophecy, and curiosity about "Christian fortune-telling" can open doors to python and other strongman spirits like Jezebel and Leviathan. You will be challenged to stop chasing every prophetic word, shut demonic entry points, and return to the secret place where true deliverance happens. As Kathy shares real stories of witchcraft attacks, medically verified healing miracles, and the power of anointing oil, you'll be equipped to cut off the head of the snake, reclaim your breath, and walk in freedom, healing, and bold prophetic authority in Jesus' name. #PythonSpirit #SpiritualWarfare #Deliverance #KathyDeGraw #PropheticVoice **Connect with Us** - Website: https://www.kathydegrawministries.org/ - Facebook: https://www.facebook.com/kathydegraw/ - Instagram: https://www.instagram.com/kathydegraw/ Podcast - Subscribe to our YouTube channel and listen to Kathy's Podcast called Prophetic Spiritual Warfare, or on Spotify at https://open.spotify.com/show/3mYPPkP28xqcTzdeoucJZu or Apple podcasts at https://podcasts.apple.com/us/podcast/prophetic-spiritual-warfare/id1474710499 **Recommended Resources:** - - Receive a free prayer pdf on Warfare Prayer Declarations at https://kathydegrawministries.org/declarations-download - Kathy's training, mentoring and e-courses on Spiritual Warfare, Deliverance and the Prophetic: https://training.kathydegrawministries.org/ - Healed At Last ~ Overcome Sickness and Receive your Physical Healing: https://www.kathydegrawministries.org/healed-at-last/ - Mind Battles – Root Out Mental Triggers to Release Peace!: https://www.kathydegrawministries.org/product/mind-battles-pre-order-available-january-2023/ -Kathy has several books available on Amazon or kathydegrawministries.org **Support Kathy DeGraw Ministries:** - Give a one-time love offering or consider partnering with us for $15, $35, $75 or any amount! Every dollar helps us help others! - Website: https://www.kathydegrawministries.org/donate/ - CashApp $KDMGLORY - Venmo @KD-Ministries - Paypal.me/KDeGrawMinistries or donate to email admin@degrawministries.org - Mail a check to: Kathy DeGraw Ministries ~ PO Box 65 ~ Grandville MI 49468
Let’s hear from the next generation of network engineers. Eric Chou sits down with Sem Eyob and Damon Hoody, two early-career network engineers, to talk about how they got into the profession and where they hope to go. They share their views on AI and its effect on their generation, their struggles finding entry level... Read more »
Let’s hear from the next generation of network engineers. Eric Chou sits down with Sem Eyob and Damon Hoody, two early-career network engineers, to talk about how they got into the profession and where they hope to go. They share their views on AI and its effect on their generation, their struggles finding entry level... Read more »
In the late 1980s, a band exploded out of LA's Sunset Strip, and their power cords spread far and wide, playing a vital role in defeating communism. That is the tale of the fictional Whyte Python and Alex and Boney loved every single moment. Author Travis Kennedy takes on the 15 minutes to wade through your hosts basically fangirling every single second. WYTHE PYTHON NEVER DIES!!!Patreon members get extra time: 15 more minutes in which you get to see behind the scenes and find out how the book was written. You can subscribe here: https://www.patreon.com/cw/15MinuteBookClubWatch the video version: https://www.youtube.com/@15MinuteBook_ClubBuy the book (UK) https://uk.bookshop.org/shop/15MinuteBookClubBuy the book (US) https://bookshop.org/shop/15MinuteBookClub Hosted on Acast. See acast.com/privacy for more information.
Topics covered in this episode: PEP 798: Unpacking in Comprehensions Pandas 3.0.0rc0 typos A couple testing topics Extras Joke Watch on YouTube About the show Sponsored by us! Support our work through: Our courses at Talk Python Training The Complete pytest Course Patreon Supporters Connect with the hosts Michael: @mkennedy@fosstodon.org / @mkennedy.codes (bsky) Brian: @brianokken@fosstodon.org / @brianokken.bsky.social Show: @pythonbytes@fosstodon.org / @pythonbytes.fm (bsky) Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Monday at 10am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Michael #1: PEP 798: Unpacking in Comprehensions After careful deliberation, the Python Steering Council is pleased to accept PEP 798 – Unpacking in Comprehensions. Examples [*it for it in its] # list with the concatenation of iterables in 'its' {*it for it in its} # set with the union of iterables in 'its' {**d for d in dicts} # dict with the combination of dicts in 'dicts' (*it for it in its) # generator of the concatenation of iterables in 'its' Also: The Steering Council is happy to unanimously accept “PEP 810, Explicit lazy imports” Brian #2: Pandas 3.0.0rc0 Pandas 3.0.0 will be released soon, and we're on Release candidate 0 Here's What's new in Pands 3.0.0 Dedicated string data type by default Inferred by default for string data (instead of object dtype) The str dtype can only hold strings (or missing values), in contrast to object dtype. (setitem with non string fails) The missing value sentinel is always NaN (np.nan) and follows the same missing value semantics as the other default dtypes. Copy-on-Write The result of any indexing operation (subsetting a DataFrame or Series in any way, i.e. including accessing a DataFrame column as a Series) or any method returning a new DataFrame or Series, always behaves as if it were a copy in terms of user API. As a consequence, if you want to modify an object (DataFrame or Series), the only way to do this is to directly modify that object itself. pd.col syntax can now be used in DataFrame.assign() and DataFrame.loc() You can now do this: df.assign(c = pd.col('a') + pd.col('b')) New Deprecation Policy Plus more - Michael #3: typos You've heard about codespell … what about typos? VSCode extension and OpenVSX extension. From Sky Kasko: Like codespell, typos checks for known misspellings instead of only allowing words from a dictionary. But typos has some extra features I really appreciate, like finding spelling mistakes inside snake_case or camelCase words. For example, if you have the line: *connecton_string = "sqlite:///my.db"* codespell won't find the misspelling, but typos will. It gave me the output: *error: `connecton` should be `connection`, `connector` ╭▸ ./main.py:1:1 │1 │ connecton_string = "sqlite:///my.db" ╰╴━━━━━━━━━* But the main advantage for me is that typos has an LSP that supports editor integrations like a VS Code extension. As far as I can tell, codespell doesn't support editor integration. (Note that the popular Code Spell Checker VS Code extension is an unrelated project that uses a traditional dictionary approach.) For more on the differences between codespell and typos, here's a comparison table I found in the typos repo: https://github.com/crate-ci/typos/blob/master/docs/comparison.md By the way, though it's not mentioned in the installation instructions, typos is published on PyPI and can be installed with uv tool install typos, for example. That said, I don't bother installing it, I just use the VS Code extension and run it as a pre-commit hook. (By the way, I'm using prek instead of pre-commit now; thanks for the tip on episode #448!) It looks like typos also publishes a GitHub action, though I haven't used it. Brian #4: A couple testing topics slowlify suggested by Brian Skinn Simulate slow, overloaded, or resource-constrained machines to reproduce CI failures and hunt flaky tests. Requires Linux with cgroups v2 Why your mock breaks later Ned Badthelder Ned's taught us before to “Mock where the object is used, not where it's defined.” To be more explicit, but probably more confusing to mock-newbies, “don't mock things that get imported, mock the object in the file it got imported to.” See? That's probably worse. Anyway, read Ned's post. If my project myproduct has user.py that uses the system builtin open() and we want to patch it: DONT DO THIS: @patch("builtins.open") This patches open() for the whole system DO THIS: @patch("myproduct.user.open") This patches open() for just the user.py file, which is what we want Apparently this issue is common and is mucking up using coverage.py Extras Brian: The Rise and Rise of FastAPI - mini documentary “Building on Lean” chapter of LeanTDD is out The next chapter I'm working on is “Finding Waste in TDD” Notes to delete before end of show: I'm not on track for an end of year completion of the first pass, so pushing goal to 1/31/26 As requested by a reader, I'm releasing both the full-so-far versions and most-recent-chapter Michael: My Vanishing Gradient's episode is out Django 6 is out Joke: tabloid - A minimal programming language inspired by clickbait headlines
Kent Beck: You're Ignoring Optionality… and Paying for ItIn this episode of Maintainable, Robby speaks with Kent Beck, a foundational voice in modern software development and author of Tidy First?. Kent joins from California to explore why optionality is a central, often underestimated dimension of maintainable software.Kent begins by describing the tension between features and future flexibility. Shipping new capabilities is easy to measure. Creating options for what comes next is not. That imbalance is where maintainability either flourishes or collapses. Senior developers in particular must learn to navigate this tension because they have lived through the consequences when no one does.They reflect on how cost models have shifted across the last five decades. Early in Kent's career, computers were expensive and programmers were cheap. Today the balance often flips depending on scale. At massive scale, electricity and compute time become meaningful costs again. That variability shapes whether teams optimize for hardware efficiency or developer efficiency.Episode Highlights[00:00:46] The Two Forms of Software ValueKent explains why software value comes from both current features and the options you preserve for future work. He describes optionality as the invisible half of maintainability.[00:03:35] When Computers Become “Expensive” AgainRobby and Kent revisit the shift from hardware-optimized development to developer-optimized development and how large-scale systems have reintroduced compute cost pressures.[00:07:25] Why the Question Mark in Tidy First?Kent shares why tidying is always a judgment call and why he put a question mark in the title.[00:10:14] The Real Cost of Speculative FlexibilityThey discuss why adding configurability too early creates waste and why waiting until just before you need it increases value.[00:13:46] Making Hard Changes EasyKent outlines his guiding idea. When you face a difficult change, make the change easy first, then make the easy change.[00:17:08] The Feature SawKent explains his features versus options graph and how teams repeatedly burn optionality until they hit zero. At that point, forward movement becomes painful.[00:19:37] Why 100 Percent Utilization Is a TrapKent discusses how queuing theory shows that full utilization pushes wait times toward infinity. Overcommitted teams have no room for design work.[00:22:44] Split Teams Do Not Solve the ProblemRobby talks about consulting scenarios where “tidy teams” and “feature teams” are separated. Kent argues that this splits incentives and prevents optionality from being sustained.[00:26:15] Structure and Behavior Should Not Ship TogetherKent describes why feature changes are irreversible, structure changes are reversible, and why combining them increases risk for everyone.[00:30:37] Tidying Reveals IntentWhile cleaning up structure, developers often uncover logic flaws or misunderstandings that were previously hidden.[00:32:00] When Teams Discourage TestingKent shares stories about environments where developers were punished for refactoring or writing tests. He explains why building career options is essential in those situations.[00:37:57] Why Tidying Is an Ethical ObligationKent reframes optionality as a moral responsibility. No one should make work harder for the next person who touches the code.[00:41:33] Succession and SlicingKent describes how nearly every structural change can be broken into small, safe steps, even when the change first appears atomic.[00:47:00] A Small Habit to Start TodayKent suggests adding a blank line to separate conceptual chunks in long functions. It is a small step that improves clarity immediately.Resources MentionedTidy First? by Kent BeckKent Beck on SubstackThe Timeless Way of Building by Christopher AlexanderThanks to Our Sponsor!Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.
Andy Lapteff once considered himself a ‘CLI lifer.’ As a network engineer he wasn’t interested in Python. He didn’t want to learn to code. He had no desire to embrace any of the developer-like processes and tools creeping into the profession, particularly around network automation. That’s changed. On today’s Heavy Networking, Andy shares the professional,... Read more »
Andy Lapteff once considered himself a ‘CLI lifer.’ As a network engineer he wasn’t interested in Python. He didn’t want to learn to code. He had no desire to embrace any of the developer-like processes and tools creeping into the profession, particularly around network automation. That’s changed. On today’s Heavy Networking, Andy shares the professional,... Read more »
Kent Overstreet joins us for a full update on bcachefs. What's new, what's next, and the surprising upside of getting kicked out of the kernel.Sponsored By:Managed Nebula: Meet Managed Nebula from Defined Networking. A decentralized VPN built on the open-source Nebula platform that we love. 1Password Extended Access Management: 1Password Extended Access Management is a device trust solution for companies with Okta, and they ensure that if a device isn't trusted and secure, it can't log into your cloud apps. CrowdHealth: Discover a Better Way to Pay for Healthcare with Crowdfunded Memberships. Join CrowdHealth to get started today for $99 for your first three months using UNPLUGGED.Unraid: A powerful, easy operating system for servers and storage. Maximize your hardware with unmatched flexibility. Support LINUX UnpluggedLinks:
Andy Lapteff once considered himself a ‘CLI lifer.’ As a network engineer he wasn’t interested in Python. He didn’t want to learn to code. He had no desire to embrace any of the developer-like processes and tools creeping into the profession, particularly around network automation. That’s changed. On today’s Heavy Networking, Andy shares the professional,... Read more »
Python's popularity in data science and backend engineering has made it the default language for building AI infrastructure. However, with the rapid growth of AI applications, developers are increasingly looking for tools that combine Python's flexibility with the rigor of production-ready systems. Pydantic began as a library for type-safe data validation in Python and has The post Pydantic AI with Samuel Colvin appeared first on Software Engineering Daily.
Recent headlines claim actress Zoë Kravitz left a pet python behind in Taylor Swift’s mansion — a story that resurfaced just as winter conditions worsened. The segment has the hosts joking, worrying (for the snake), and wondering how wild fame gets when pets and parties mix. See omnystudio.com/listener for privacy information.
The show opens with a nationwide chill as the U.S. braces for record-breaking freezing temperatures thanks to a powerful arctic blast sweeping across much of the country. Forecasters warn that more than 200 million Americans will be plunged into sub-freezing conditions, with many regions expecting historically cold highs and lows this week. Against that backdrop, celebrity gossip heats up: recent headlines claim actress Zoë Kravitz left a pet python behind in Taylor Swift’s mansion — a story that resurfaced just as winter conditions worsened. The segment has the hosts joking, worrying (for the snake), and wondering how wild fame gets when pets and parties mix. Jumping from pets to partnerships, the show dissects news that reality-star Kandi Burruss claims her estranged husband’s prenup is invalid, insisting he’s not being faithful — a revelation that ignited debate about trust, money, and marriage under public scrutiny. Website: https://www.urban1podcasts.com/rickey-smiley-morning-show See omnystudio.com/listener for privacy information.
Talk Python To Me - Python conversations for passionate developers
A lot of people building software today never took the traditional CS path. They arrived through curiosity, a job that needed automating, or a late-night itch to make something work. This week, David Kopec joins me to talk about rebuilding computer science for exactly those folks, the ones who learned to program first and are now ready to understand the deeper ideas that power the tools they use every day. Episode sponsors Sentry Error Monitoring, Code TALKPYTHON NordStellar Talk Python Courses Links from the show David Kopec: davekopec.com Classic Computer Science Book: amazon.com Computer Science from Scratch Book: computersciencefromscratch.com Computer Science from Scratch at NoStartch (CSFS30 for 30% off): nostarch.com Watch this episode on YouTube: youtube.com Episode #529 deep-dive: talkpython.fm/529 Episode transcripts: talkpython.fm Theme Song: Developer Rap
We often look for ways to reduce the load on our brains, seeking shortcuts and optimizations to get ahead. Sometimes this works, reinforcing the belief that we can hack our way around every problem. However, this episode addresses the truth that many fundamental aspects of your career require something difficult, messy, slow, or inefficient, demanding deep thought and repeated failure.This episode details the difficult truths about facing the most essential challenges in your career:Understand the Hard Path: Recognize that many aspects of your career, skill set, relationships, and hobbies require something difficult, messy, slow, or inefficient, demanding deep thought and repeated failure.Identify Your Primary Obstacles: Pinpoint the hard things you are procrastinating on, such as developing essential domain knowledge, deepening relationships with crucial co-workers or your manager, or getting the necessary "reps" of difficult building and practice.The Path to Mastery: Realize that becoming a great engineer (e.g., a great Python developer) is achieved not by reading books or finding perfect tools, but by building things over and over. This practice includes receiving feedback from peers and applying what you learn under challenge.The Pain of Decision: Explore why it is difficult to even decide to do a hard thing. By committing to the challenging path, you are choosing to cut off your optionality and giving up the hope of finding an easier, lower-investment alternative.Sustaining Commitment: Understand that initial motivation or an energetic feeling will not carry you through the obstacle when the development process becomes awkward, slow, or frustrating. Staying committed requires reinforcing your core underlying reason for doing the hard work.The Reward: Recognize that if you successfully address the hard thing you know needs doing, everything else in your life and career becomes easier.
© 2020-2026 Ivy Podcast Discovery LLC
