R
Rob Fitzpatrick
Guest
Actually I was being lazy; I meant to say "language & tools"; I wasn't trying to separate them. I think inevitably when you open the "floor" for questions there's a chance to go off into the weeds. So while it may not please some people it's probably good to gently enforce some amount of discipline about scope in these webinars. Assuming that happens, once we do a few of these sessions people will come to understand what to expect and it should become easier keep the conversation on point. Jean is planning a separate Q&A for Community so I think that's the place to deal with ideas about Ideas, site improvements, etc. And we get "the road ahead" info in quarterly updates and conference keynotes and info exchanges (which are typically made available after the fact to non-attendees). So I would like to see dev Q&A and DB Q&A sessions focused on people's experiences with the products they run today. Within that scope there's still a lot to talk about: limitations, bugs, how-tos, best practices, worst practices, lessons learned, propeller-head internals, third-party integration patterns, etc. Inevitably you'll also hear some amount of "I hate feature X", "feature Y is borked", "we need feature Z", etc., and the moderators can funnel that stuff through to PM-land after the fact. Or the PMs can just watch the recordings after the fact. 
Continue reading...
Continue reading...