My Problem 🤔
Every June I hear people talking about the big premiere of the season. The summer movie, the new season of some show, the sequel they had been waiting on for years. And I nod and think about my own thing: in a few days WWDC arrives.
My problem is that it’s very hard to explain that feeling to someone outside Apple’s development ecosystem. Saying you’ve had the date marked on the calendar for weeks, that you take Keynote day as a holiday, that your nerves go up as the hour approaches — said without context, it sounds odd. For anyone who doesn’t program in Swift, a two-hour keynote talking about APIs is the furthest thing from a movie premiere.
It’s not just nerd stuff. WWDC has something no premiere has: what they announce directly affects my work, the decisions I made six months ago that will now get an official answer. When the lights go down in my private screening room, I’m not just another spectator — I’m the target audience.
My Solution 🧩
I stopped trying to justify it. WWDC is my premiere of the year, and I enjoy it more than any movie or TV show. I have a blast like a kid.
The week before
It starts before Monday. Rumors peak, the community is in full speculation mode, and I’ve spent days thinking about what they’re going to announce and how it will affect what I’m working on. It’s the same energy as the week before a highly anticipated premiere, with one fundamental difference: the outcome actually matters to me — as someone whose job changes based on what’s announced.
The Keynote as a ritual
In Spain, the Keynote hits at 7:00 PM. The perfect hour — I wrap up the workday, early dinner, and from then on only the Keynote exists.
My ritual includes a screen setup that would look absurd from the outside. On the main one, Apple’s official stream. On a second one, a group of nutters doing live commentary — they comment every slide, predict the next, react in real time. And on a third, I follow X, technical blogs, and developer Slacks and Discords: nuances missed in the slides and first analyses of the real impact.
What I love most is that the Keynote mixes two things that rarely go together: the thrill of the show and the technical information that changes my work. I process every feature on two levels at once — spectator enjoying it and developer already thinking about how to integrate it.
And then there are the “yes!” moments — when they announce something you’d been asking for. Last year, with the improvements to Swift Concurrency, I jumped off the couch. Literally.
The sessions are the real content
The Keynote is the appetizer. The technical sessions are the main course, and they last for weeks.
I go through the catalog like someone browsing the lineup of a film festival. With over a hundred sessions, selecting and prioritizing is an activity in itself. And they don’t expire: Apple keeps them on developer.apple.com indefinitely. June is for the new stuff, and the rest of the year is for going deeper into the ones I left for later.
This connects with Swift Pills: dense knowledge that deserves to be consumed at a calm pace. And with Apple Coding Speed: the comprehension speed you train is what lets you get the most out of every session.
The betas as a playground
The day of the Keynote, the betas open up. From there the game begins: install, compile against the new SDK, see what breaks, explore the APIs before they have complete documentation. It’s early access, but I’m the one playing while I develop — and what I discover can shift design decisions I’ve been mulling over for months.
The community in WWDC mode
The technical conversation among Apple developers goes through the roof. Everyone has something to comment on, something they discovered, some detail that changed how they saw a problem.
The conferences in the ecosystem — like the ones I follow in Conferences 25 — have that energy, but WWDC takes it to the extreme: it’s the moment of the year when the entire community looks at the same thing at the same time.
My Result 🎯
I no longer try to explain it. I accept that WWDC is my event of the year and I enjoy it without hang-ups.
What it gives me every June:
- Genuine anticipation — the event that directly affects my work
- The Keynote as a show — two hours in dual mode: spectator and developer
- Technical sessions that last months — dense material I consume calmly the rest of the year
- The betas as a lab — early access to the new APIs before anyone else
- The community at its peak — the richest technical conversation of the year
- Answers to problems sitting on your desk — unmatched satisfaction
If you have an event of the year that makes you feel like a kid, don’t justify it. Enjoy it. Mine is WWDC, and I’m already looking forward to the next one.
Keep coding, keep running 🏃♂️