logo FEDIDEVS

PyCascades 2024

Ooh! @pycascades 2025 will be held at Revolution Hall!

2025.pycascades.com/attending/

Can't wait for tickets to be on-sale as it would be the first time I would be able to go in-person.

9 3 2

Maybe you wanted to give a talk at or one of our friends like , , or but it didn't work out? Maybe you saw or learned something that got you inspired?

is coming in July, and our CFP is open for the next ~20 hours -- we'd LOVE to hear from you while we still can! We gladly welcome speakers of all experience levels (ā¤ļø new folks!) and a wide array of topics -- if you're excited about something, share it!

pyohio.org/2024/speaking/cfp/

Boosts appreciated!

12 18 0

I have a / ā€œmissed contact" question; I spoke to a Tammy who was at and PyCon US, and we talked about GitHub's contribution graph; if anyone knows who that is, can you put her in touch? Thanks!

2 3 2

please note - this was about 2024. Our Portland venue for 2025 is not boatable, and I cannot in good conscience recommend kayaking in Portland in February.
will have to wait hachyderm.io/@bengerman/112209

2 0 0

Those asking about the talk: I don't know whether they'll be posted, but the speaker has put a text version online: github.com/madrury/the-rising-

My key point is ā€œmodel the problem in fine enough detail that the solution is self evidentā€ vs ā€œThe Darknessā€. It is the same problem when you allow the structure of your web API or the idiosyncracies of your data storage create pressure on the design of your business code.

4 0 1

Things Iā€™ve been thinking about a lot lately:

- code design pressure (good: testability, bad: coupling business code with validation and/or storage ā€“ interestingly thereā€™s been a talk about just that, framed using an obscure German mathematician)

- type state pattern, or: why I don't use state machines. This has nothing to do with static types but a continuation of ā€œmake illegal state unrepresentableā€. Practically, this means that youā€™ll rarely see an `| None` in my class fields.

8 3 7

Had a great time at the sprint. Always great to have a whole day to dip in and out of conversations, help people, and write some code. And network with other maintainers to find out weā€™re all thinking about and dealing with the same things.

8 0 0

I joined the PursuedPyBear @ppb sprint table, and fixed an issue where rectangles were rendering as squares! šŸ˜µā€šŸ’« github.com/ppb/pursuedpybear/p

6 3 0

Me arriving on a Monday morning at the University of Washington for sprints just after the end of a class.

Some of them even gave me a deferential nod; presumably because they suspected Iā€™m their new professor or something. Almost fell to dust.

13 0 1

I am loving the PyLadies panel at @pycascades šŸ’–šŸ’–šŸ’–

@mariatta's efforts as a core Python developer to the development tools and making sure the language summit is not all men ever again is truly incredible.

@christyheaton shared how her organizing work started and how it was really helpful to just jump in and start giving talks. Find a topic or project you like (in her case mapping in Python) and just speak about it everywhere!

14 5 0