#pycon2025 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #pycon2025, aggregated by home.social.
-
YEAR IN REVIEW: Social/health
- Very bad #MentalHealth, including a real mid-life crisis (not done)
- Ate w/ strangers indoors >0 times, thanks to nasal sprays, leading to…
- A relatively fun, social #PyCon2025
- Got a li'l closer to being a full-time #pescatarian
- Incredible amount of family drama, jfc (not done)
- Switched my caffeinated mint brand
- Got back to my #tea habit
- First new pair of glasses since moving back East
- Incredible run of lovely weather late summer/early fall -
YEAR IN REVIEW: Social/health
- Very bad #MentalHealth, including a real mid-life crisis (not done)
- Ate w/ strangers indoors >0 times, thanks to nasal sprays, leading to…
- A relatively fun, social #PyCon2025
- Got a li'l closer to being a full-time #pescatarian
- Incredible amount of family drama, jfc (not done)
- Switched my caffeinated mint brand
- Got back to my #tea habit
- First new pair of glasses since moving back East
- Incredible run of lovely weather late summer/early fall -
YEAR IN REVIEW: Social/health
- Very bad #MentalHealth, including a real mid-life crisis (not done)
- Ate w/ strangers indoors >0 times, thanks to nasal sprays, leading to…
- A relatively fun, social #PyCon2025
- Got a li'l closer to being a full-time #pescatarian
- Incredible amount of family drama, jfc (not done)
- Switched my caffeinated mint brand
- Got back to my #tea habit
- First new pair of glasses since moving back East
- Incredible run of lovely weather late summer/early fall -
YEAR IN REVIEW: Social/health
- Very bad #MentalHealth, including a real mid-life crisis (not done)
- Ate w/ strangers indoors >0 times, thanks to nasal sprays, leading to…
- A relatively fun, social #PyCon2025
- Got a li'l closer to being a full-time #pescatarian
- Incredible amount of family drama, jfc (not done)
- Switched my caffeinated mint brand
- Got back to my #tea habit
- First new pair of glasses since moving back East
- Incredible run of lovely weather late summer/early fall -
YEAR IN REVIEW: Social/health
- Very bad #MentalHealth, including a real mid-life crisis (not done)
- Ate w/ strangers indoors >0 times, thanks to nasal sprays, leading to…
- A relatively fun, social #PyCon2025
- Got a li'l closer to being a full-time #pescatarian
- Incredible amount of family drama, jfc (not done)
- Switched my caffeinated mint brand
- Got back to my #tea habit
- First new pair of glasses since moving back East
- Incredible run of lovely weather late summer/early fall -
🌏 Coming to PyCon AU from overseas?
If you're traveling from outside Australia, now is the time to get your visa sorted!
We’ve just published updated information to help you prepare your visa application. Visa processing can take time, so check it out and don't be late!
-
🌏 Coming to PyCon AU from overseas?
If you're traveling from outside Australia, now is the time to get your visa sorted!
We’ve just published updated information to help you prepare your visa application. Visa processing can take time, so check it out and don't be late!
-
🌏 Coming to PyCon AU from overseas?
If you're traveling from outside Australia, now is the time to get your visa sorted!
We’ve just published updated information to help you prepare your visa application. Visa processing can take time, so check it out and don't be late!
-
🌏 Coming to PyCon AU from overseas?
If you're traveling from outside Australia, now is the time to get your visa sorted!
We’ve just published updated information to help you prepare your visa application. Visa processing can take time, so check it out and don't be late!
-
🌏 Coming to PyCon AU from overseas?
If you're traveling from outside Australia, now is the time to get your visa sorted!
We’ve just published updated information to help you prepare your visa application. Visa processing can take time, so check it out and don't be late!
-
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 -
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 -
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 -
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 turned my #pycon2025 poster about vector embeddings into a blog post:
https://blog.pamelafox.org/2025/05/a-visual-exploration-of-vector.html -
I turned my #pycon2025 poster about vector embeddings into a blog post:
https://blog.pamelafox.org/2025/05/a-visual-exploration-of-vector.html -
I turned my #pycon2025 poster about vector embeddings into a blog post:
https://blog.pamelafox.org/2025/05/a-visual-exploration-of-vector.html -
I turned my #pycon2025 poster about vector embeddings into a blog post:
https://blog.pamelafox.org/2025/05/a-visual-exploration-of-vector.html -
I turned my #pycon2025 poster about vector embeddings into a blog post:
https://blog.pamelafox.org/2025/05/a-visual-exploration-of-vector.html -
Takeaways:
1. Your business code is sacred
2. Protect it from your tools
3. Write tests; get a better designhttps://ox.cx/design for more!
And follow Hynek on YouTube at @THE_HYNEK
-
Takeaways:
1. Your business code is sacred
2. Protect it from your tools
3. Write tests; get a better designhttps://ox.cx/design for more!
And follow Hynek on YouTube at @THE_HYNEK
-
Takeaways:
1. Your business code is sacred
2. Protect it from your tools
3. Write tests; get a better designhttps://ox.cx/design for more!
And follow Hynek on YouTube at @THE_HYNEK
-
Takeaways:
1. Your business code is sacred
2. Protect it from your tools
3. Write tests; get a better designhttps://ox.cx/design for more!
And follow Hynek on YouTube at @THE_HYNEK
-
Takeaways:
1. Your business code is sacred
2. Protect it from your tools
3. Write tests; get a better designhttps://ox.cx/design for more!
And follow Hynek on YouTube at @THE_HYNEK
-
Whenever possible, start with the domain model, then start ✨engineering✨
"Complexity is not about how many keys I have to press -- it's about how difficult it is to reason about the consequences of what I'm doing"
- @hynek
-
Whenever possible, start with the domain model, then start ✨engineering✨
"Complexity is not about how many keys I have to press -- it's about how difficult it is to reason about the consequences of what I'm doing"
- @hynek
-
Whenever possible, start with the domain model, then start ✨engineering✨
"Complexity is not about how many keys I have to press -- it's about how difficult it is to reason about the consequences of what I'm doing"
- @hynek
-
Whenever possible, start with the domain model, then start ✨engineering✨
"Complexity is not about how many keys I have to press -- it's about how difficult it is to reason about the consequences of what I'm doing"
- @hynek
-
Whenever possible, start with the domain model, then start ✨engineering✨
"Complexity is not about how many keys I have to press -- it's about how difficult it is to reason about the consequences of what I'm doing"
- @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)
-
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)
-
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)
-
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)
-
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.
-
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.
-
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.
-
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.
-
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.
-
Conflicting goals exist in all meaningful apps
The Web API is dictated by what is best for the user, what's a good external standard, etc
The Database Schema is motivated by effective data storage, developer affordances, and performance
The Domain Model is dictated by the Business Requirement
-
Conflicting goals exist in all meaningful apps
The Web API is dictated by what is best for the user, what's a good external standard, etc
The Database Schema is motivated by effective data storage, developer affordances, and performance
The Domain Model is dictated by the Business Requirement
-
Conflicting goals exist in all meaningful apps
The Web API is dictated by what is best for the user, what's a good external standard, etc
The Database Schema is motivated by effective data storage, developer affordances, and performance
The Domain Model is dictated by the Business Requirement
-
Conflicting goals exist in all meaningful apps
The Web API is dictated by what is best for the user, what's a good external standard, etc
The Database Schema is motivated by effective data storage, developer affordances, and performance
The Domain Model is dictated by the Business Requirement
-
Conflicting goals exist in all meaningful apps
The Web API is dictated by what is best for the user, what's a good external standard, etc
The Database Schema is motivated by effective data storage, developer affordances, and performance
The Domain Model is dictated by the Business Requirement
-
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.
-
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.
-
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.
-
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.
-
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.
-
Next pressure: The Rising Sea.
The example here is a box-moving problem from Advent of Code.
Good solutions reflect a well-formulated Domain Model, a model of code and data that describes the domain of your business or problem
Good solutions often include The Darkness, the messy layer that connects the outside world to your Domain Model
-
Next pressure: The Rising Sea.
The example here is a box-moving problem from Advent of Code.
Good solutions reflect a well-formulated Domain Model, a model of code and data that describes the domain of your business or problem
Good solutions often include The Darkness, the messy layer that connects the outside world to your Domain Model
-
Next pressure: The Rising Sea.
The example here is a box-moving problem from Advent of Code.
Good solutions reflect a well-formulated Domain Model, a model of code and data that describes the domain of your business or problem
Good solutions often include The Darkness, the messy layer that connects the outside world to your Domain Model
-
Next pressure: The Rising Sea.
The example here is a box-moving problem from Advent of Code.
Good solutions reflect a well-formulated Domain Model, a model of code and data that describes the domain of your business or problem
Good solutions often include The Darkness, the messy layer that connects the outside world to your Domain Model
-
Next pressure: The Rising Sea.
The example here is a box-moving problem from Advent of Code.
Good solutions reflect a well-formulated Domain Model, a model of code and data that describes the domain of your business or problem
Good solutions often include The Darkness, the messy layer that connects the outside world to your Domain Model
-
This relates to how tightly coupled code is. Two pieces of code are coupled if they can only be understood by looking at both pieces
Testable code is better code for a number of reasons, but one of them is decoupling
This is the first pressure we're talking about, and it's a good one!
-
This relates to how tightly coupled code is. Two pieces of code are coupled if they can only be understood by looking at both pieces
Testable code is better code for a number of reasons, but one of them is decoupling
This is the first pressure we're talking about, and it's a good one!
-
This relates to how tightly coupled code is. Two pieces of code are coupled if they can only be understood by looking at both pieces
Testable code is better code for a number of reasons, but one of them is decoupling
This is the first pressure we're talking about, and it's a good one!
-
This relates to how tightly coupled code is. Two pieces of code are coupled if they can only be understood by looking at both pieces
Testable code is better code for a number of reasons, but one of them is decoupling
This is the first pressure we're talking about, and it's a good one!
-
This relates to how tightly coupled code is. Two pieces of code are coupled if they can only be understood by looking at both pieces
Testable code is better code for a number of reasons, but one of them is decoupling
This is the first pressure we're talking about, and it's a good one!
-
Business logic has consequences! User's lives can be affected or ended based on our code.
Canonical reference: Therac-25. Every programmer should look this up.
Business logic is the most important code in your application
This is where Design Pressure comes into play.