4 ms·

So one interesting thing is that the "two disparate events, one conference" problem goes a little deeper. There seem to be four "things" you get out of WWDC:

So one interesting thing is that the "two disparate events, one conference" problem goes a little deeper. There seem to be four "things" you get out of WWDC: 1. Meeting with people (can be achieved without a ticket and just going to SF that week) 2. The sessions (many of which are recorded and thus largely don't require a ticket, but some are not I think?) 3. The keynote (not actually important for developers) 4. 1-on-1 with engineers. As far as I can tell the only truly unique and universally considered valuable aspect of the conference that absolutely requires a ticket. So it seems that (4) is the real value here, probably more to do with the fact that its so hard to get developer help from Apple any other time of the year. Since you mention radical changes, I wonder if it would be worth it for Apple to just prerecord ALL sessions, make them all available after a Keynote that has nothing to do with the conference, and then offer a WWDC week that just focused on direct contact with engineers. This would actually be better for the sessions too: many times I've had a question about a session, and either there wasn't time to answer it then, or I didn't think of it until much later. By having a conference full of people that had plenty of time to review content beforehand, you'd probably get more questions answered.

mikeash 14y ago
I think that #1 is still enormously enhanced by the conference itself. You don't get the same experience if you just hang out in the area that week. (Or I assume you don't, I've not tried it.) The serendipitous socialization aspects are a big deal, even only looking at doing it with people who don't work at Apple. I agree that #2 isn't all that important (although there are probably some people who learn better in that sort of environment) and #3 is basically just a free show that you get with your ticket and could easily be made completely separate. I like the idea of a week that's just focused on direct contact with engineers, but I fear that it would end up in very inefficient uses of their time due to being flooded with people asking basics because they couldn't be bothered to watch the intro sessions. In general, I fear what would happen without enough structure. But perhaps it could be made to work, and it certainly seems worth considering. The obvious first step seems like a bigger venue, though. Apple keeps saying they can't... but other companies pull it off, so I have to wonder why Apple can't.

mikeash 14y ago

I think that #1 is still enormously enhanced by the conference itself. You don't get the same experience if you just hang out in the area that week. (Or I assume you don't, I've not tried it.) The serendipitous socialization aspects are a big deal, even only looking at doing it with people who don't work at Apple. I agree that #2 isn't all that important (although there are probably some people who learn better in that sort of environment) and #3 is basically just a free show that you get with your ticket and could easily be made completely separate. I like the idea of a week that's just focused on direct contact with engineers, but I fear that it would end up in very inefficient uses of their time due to being flooded with people asking basics because they couldn't be bothered to watch the intro sessions. In general, I fear what would happen without enough structure. But perhaps it could be made to work, and it certainly seems worth considering. The obvious first step seems like a bigger venue, though. Apple keeps saying they can't... but other companies pull it off, so I have to wonder why Apple can't.