Our PyLadiesCon recap from PyCon US 2025 is live! 
We had an unforgettable time in Pittsburgh — connecting with the global Python community, sharing our mission, and celebrating together!
From lightning talks and the PyLadies Lunch to building support for our next edition, it was a weekend full of impact and joy.
Read the full recap: 
https://conference.pyladies.com/2025-pyladiescon-pycon-us/
I'm proud of my spouse @leonardr for his decades of service to the world. The #Python Software Foundation recently recognized some of that service by naming him a @ThePSF Fellow, and giving him the Community Service Award.
A few photos of the ceremony at #PyConUS 2025: https://harihareswara.net/posts/2025/congratulating-leonard-psf-award/
My PyConUS 2025 talk, "Processing Large JSON Files Without Running Out Of Memory", is now up on YouTube:
Next year's #PyConUS seems to take place in Long Beach, CA. Tempting... but not right now 
https://lists.iana.org/hyperkitty/list/tz@iana.org/thread/OFFEEPFUHD4M4SUP4Y3CZ4BF74B6KVFL/
For people who weren’t at #PyConUS, here is a web version of the poster by @vincesalvino and @thibaudcolas about building low-carbon websites 
https://wagtail.org/blog/pycon-us-2025-building-low-carbon-websites/ with links and all
I wrote up my tips for teaching Python with GitHub Codespaces, based off what I shared during the #PyconUS Education Summit session:
https://blog.pamelafox.org/2025/06/teaching-python-with-codespaces.html
(It's actually a lot about how to set up dev containers with Dockerfile/docker-compose, which is helpful even if you're not teaching)
Everyone’s loving the avatars @pycon — so I had to make one for our amazing Devs-in-Residence @ThePSF too. This photo? Epic.
@ambv @sethmlarson @miketheman #PyConUS #pycon2025
I was VERY pleasantly surprised by how well my #PyConUS talk resonated! Over the past ~1.5 years I bounced the idea off people of all stripes & got very mixed responses. That helped me to shape the content but also tempered my expectations and I begged everyone who would listen to come to my talk out of fear to speak to an empty room.
I ended up speaking to an standing room only and for the first time in over ten years a talk of mine landed on HN frontpage with largely positive comments. 1/2
FlaskCon 2025 videos are listed on PyVideo.org as well, along with all the previous years! https://pyvideo.org/events/flaskcon-2025.html #Python #Flask #PyConUS #FlaskCon
Watching @hynek‘s #pyconus talk/rant on domain design on the way to the next #Python event. Which has awesome readable slides you can totally watch on phone on a plane/train, so nothing can stop you from feeling guilty about your current production design choices. I can highly recommend it, especially if you’re a fan of Pydantic.
Takeaways:
1. Your business code is sacred
2. Protect it from your tools
3. Write tests; get a better design
https://ox.cx/design for more!
And follow Hynek on YouTube at @THE_HYNEK
If you follow this method, Hynek argues that you have lost control over your domain model and therefore over your business logic.
It's ok to have duplicative-looking types at the edges of your project! Like the web interface and the DB layer
You might have three (or more!) classes for the same thing and that's OK.
(with a h/t to Adam Montgomery)
There are multiple approaches to solving this tension!
I won't write down the first one because @hynek asked us not to.
But the next way (which is apparently worse?) is to use class-based validators and an ORM as the bread in a sandwich of your business logic
They do not make good bread and your domain model gets squeezed to death.
All the shitty stuff should happen on the outside layer of your program.
Once it's inside, make it as nice as possible.
The shape of the data determines the shape of the code.
Why do we write software?
We write software to achieve a goal using tools. The core of what we're trying to accomplish is the "Business logic"
Business logic is the code that processes the data coming in to you application and does something with it to solve business needs
My mind’s still in Pittsburgh. Suitcase half-zipped. PyCon US 2025 ended, but the stories keep compiling.
There was laughter. Lightning talks. Keynotes that hit deep. An auction that spiraled into community-fueled chaos. Panels got real. Retro consoles booted up. Some even sprinted… for ice cream.
It wasn’t just a conference. It was Python-powered reunion—with stickers, stories, and heart.
Here's my recap: https://georgiker.com/blog/pycon-us-2025/
#PyConUS #PyLadies #Python
All that to say, #PyConUS 2025 was the best it could've been under the given grim circumstances. I can't thank the organizers enough and I'm returning with a full heart, ready and willing to serve. 7/7
One thing that crystalized to me this #PyConUS is that I judge my conferences by the amount of meaningful social interactions. There's always more ppl that I want to hang out with than I end up, especially given that I had some kind of vocal chord injury and didn’t take advantage of all nights 1/7
