I got sick the day PyCon started in full.
My goals for the event were simple: meet people and companies, learn what was cutting edge in Python, and do some good old-fashioned networking. Waking up that morning, something already seemed wrong, though I couldn't tell if it was the four hours of plane sleep I'd gotten the day before or something else. The uncertainty vanished quickly when I threw up.
So there I was: fresh out of the sponsor talks, having just begun stretching my wings at the expo, lying in bed staring at the ceiling. Worse, I'd been pacing myself — saving the entries I was most interested in (Microsoft, AWS, a few others) for after I made my way linearly through the rest of the expo hall. I'd also wanted to give a lightning talk about what makes good code. That idea was dead in the water too.
I missed the entirety of Friday. Built up the energy to head to the con on Saturday to do nothing but listen to talks, and quickly determined I wasn't even up for that. Wasn't sure I was up for the bus either, so I struggled my way through a sweaty two-mile walk back to the hotel.
By Sunday I had recovered fully, and my top goals seemed to have all left me behind. There were no more lightning talk slots. The expo had ended the day before. Almost all the talks I'd pegged as interesting were concluded — one of the few survivors had been rescheduled to a slot I'd already missed.
So what did I actually learn from PyCon, if I missed the majority of the con?
What actually happened
I did the career fair properly. Not the speed-run version I'd planned for the expo, but real conversations with the companies still around on Sunday. One of the guys I ended up at lunch with turned out to be the founder of a small company at the fair, and we hit it off.
I talked about my experience over lunch. I didn't get my good-code message out to the audience I'd imagined giving a lightning talk to — but I got an audience, and the combination of lead-TA work plus modern SWE experience turned out to be a more unusual angle than I'd realized. People wanted to hear about it.
I went to the talks I could still go to. Ended up learning about lazy imports from the people who proposed PEP 810 themselves. Less than I wanted to learn, but still a new feature on the cutting edge, that can resolve things such as circular dependencies.
And then the sprints. Two days, and the numbers came out something like:
- 6 PRs merged
- 1 issue opened
- 1 cross-repository chicken-and-egg problem unraveled in BeeWare's infrastructure setup
- 1 connection to a former AWS engineer willing to plug me into his network
The reflection
I went into PyCon with three goals: meet people and companies, learn what was cutting edge, and network. I came out having done all three — just none of it on the schedule I'd written for myself. The career fair replaced the expo. Lunch conversations replaced the lightning talk. Listening to the PEP 810 authors replaced a YouTube thumbnail I would have skipped. The sprints replaced everything else, and gave me the most concrete output of the whole trip.
The lesson isn’t “things work out.” I am certain that had I not gotten sick, I could have gotten much more out of PyCon. I missed real opportunities, and I do not want to pretend otherwise.
The lesson is that the schedule was never the point.
I had mistaken my plan for my goals. The plan was: visit these booths, attend these talks, give this lightning talk. The goals were: learn what is new, find people worth talking to, and put myself in places where good professional accidents could happen.
Once the original plan collapsed, the useful question was not “How do I recover the conference I meant to have?” It was “Given the conference that still exists, where is the remaining surface area?”
That changed how I used the rest of the trip. I stopped trying to recreate Friday. I went where people were still present, had the conversations still available, and contributed where contribution was still possible. The result was narrower than the trip I had imagined, but much more concrete than I expected: merged PRs, real technical learning, and relationships I would not have made by simply executing my original checklist.
So what I learned from PyCon was not just a Python trick, though I learned some of those too. It was a lesson about agency under constraint.
A plan is useful because it points you toward value. But when the plan breaks, the value may still be there. You just have to stop mourning the itinerary quickly enough to notice the room you are still in.