View  Info
Compare   Restore  
   Revision #5 - 4/27/2010 2:18 AM     

Podcast 087

Atwood: Skype doesn't do multi-cast video

Spolsky: Seriously? It's like you can't even...

Atwood: Only point-to-point

Cartaino: Really

Atwood: Yeah

Cartaino: I'm surprised

Atwood: We knew that from the VC call remember?

Spolsky: Ah, I dunno, I've never had video before. Wait, why does it say "Missed conference call"? Oh cos that was the other computer. I got Skype logged on to two computers. I got a whole new setup this week. Hey welcome to the StackOverflow Podcast X... X... X... X...

Atwood: 87 maybe?

Spolsky: No this is the special, it's like the special edition, it's like we've broken the inter-regnum.

Atwood: Oh, it's kind of like when the Eagles got back together

Spolsky: Heh heh heh, or like the [?] concert in Central Park

Atwood: That's right, I believe the title was "Hell Freezes Over"

Spolsky: The Eagles one?

Atwood: Yeah

Spolsky: Yeah. Err, that's good, that's a good one. Pigs flying is another good one. Why are they making all that noise in the kitchen? Hold on. We have with us in the audience today the special guest Robert Cartaino. Have we ever announced to the public at large?

Atwood: No, not yet, but we will, we want to, we will. He's gonna... I'm gonna... yeah... it's in the works. By the time this podcast is published it should be known.

Spolsky: Excellent plan. Robert is the new Community Manager, although I dunno what title we're going to put on his business card for StackOverflow Inc.

Cartaino: I've been putting Community Coordinator on. I don't know if that's apt, but it seems to work for now. 

Spolsky: Coordinator? OK. Alright, coach, team leader, contessa. I always say any title you think is appropriate you can have. 

Cartaino: I guess my role today is to laugh at Joel's jokes, so...

Spolsky: ...Jeff doesn't have to.

Cartaino: Yeah.

Atwood: Joel's jokes are too subtle sometimes, I don't actually... I don't actually get them until like afterwards when I'm listening to the podcast.

Spolsky: Like "Contessa - BWHA HA HA!"

Cartaino: You just have to splice them back in as an effect.

Atwood: That's right, we need a laugh track.

Spolsky: I will sometimes do that in the post-edit, post-production, I'll take Jeff's and I'll move them to other places in the podcast.

Cartaino: Ah, so now we nailed it.

Atwood: No, I don't think Joel does that. So let me talk briefly about why Robert is a member of the team. I think this fits well with we're going to get heavily into StackExchange 2.0 today and what that's about. Hopefully a lot of Q&A about that ideally. But certainly one thing we've learned with StackOverflow and SuperUser and ServerFault is that the software part is - I don't want to say it's trivial, because it's not - software is what we do - but that ends up being the easier part of the challenge. The real challenge in building community is the sociological and urban planning aspects of like how do you have a community that doesn't blow up, people don't kill each other.

Spolsky: Or even worse - that nobody goes to because they can't, because they don't care enough. 

Atwood: Or it's a ghost town and nobody cares and there's litter all over the streets. I mean these are urban planning problems and I think that's what... If we've gotten good at anything, it's not like compiling code, it's hopefully that we've figured out, at least for some kinds of community, not for every community in the world, but for some kind of communities, we've come up with a new tool, a screw-driver or pipe-wrench or whatever fits, that seems to work really well. The software does part of it, but the growing community part of it, that's what StackExchange 2.0 is all about, it's like how do you put rules and guidelines around, how do I build a community of people interested in topic X? And that is what we're looking at and that is why Robert is going to be so pivotal because he's doing sociology basically. He's helping us work out what's working and what's not working.

Spolsky: More like social work than sociology. 


Cartaino: Anthropology

Spolsky: Your job, Robert is to find the homeless guy who's also crazy and probably has cancer and get him help for all his problems. 

[More laughter]

Spolsky: Even though he doesn't want to be helped and he's blabbing on about something about the Kennedys. 

Atwood: Well, when we were in New York, Joel, there was some guy that came into a store, followed us, that was yelling at us because he felt like we were taking pictures of him.

[Joel sniggers]

Spolsky: So, question: Were you taking pictures of him?

Atwood: No, we weren't

Spolsky: Just checking

Atwood: The guy had some issues obviously.

Spolsky: Yeah. 

Atwood: That does actually happen, you joke about it, but that actually happened to us in New York City, so that was kinda weird. I also want to emphasise that Robert is, indeed, technical. I don't think we'll ever hire anybody for the company that isn't fairly deeply technical. Robert is a programmer like us, but, I think, Robert, you have a pretty deep background in some of this stuff, right? Like you've been doing, since the BBS days.

Cartaino: Yeah, I've been, I wrote my first BBS, I didn't write the first one, but I did write the first successful one. So I have a pretty low-level understanding of, you know, what it takes to get one of these systems [?] and databases working and that sort of thing. I hope I can bring some of that experience or at least pass it on to customers when they ask for crazy features that I just know aren't doable always, so 

Spolsky: Speaking of crazy features...

Cartaino: Yeah, you know, people ask for things, but you know, sometimes it's just not practical.

Spolsky: Or not possible.

Cartaino: Yeah, but I'm amazed, I'm amazed at some of the stuff you guys get in there. I mean, there's some database queries that you know.

Spolsky: I'm actually, I'm amazed that it's fast, because I think you can just tell that there are a lot of database queries on every page.

Cartaino: Yeah, I've seen feature requests come through and been like "Oh my God, there's no way they can do that.

[Talking over one another]

Spolsky: I started programming for the web was the Netscape web server and, err, C, might have been C++ and wrote with some libraries from C++ where you could do advanced things like use strings. And we were talking to a Sybase database and I remember saying "You know what, my goal is going to be one query per page. No more than that. You cannot get good performance if you get more than one query per page and so I will structure my databases in such a way that you can usually construct an entire page with the one query." Sigh, that never...

Atwood: Well, there's actually some new theory on that. That the network and the databases and the infrastructure is so fast now that they do this coalescing thing where you send lots of small queries though that because they're small, I mean this is like queuing theory. If you have really small units of work, this is like, RISC versus CISC again, so you have really small units of work, that can move through the pipeline quite rapidly. It's when you have... [Joel attempts to interrupt] but... but... my point is that if you take it to extremes it's probably bad. So if you say "Well we're only going to do one query per page", but your query is like this mongo ten hundred line abomination that, you know, it has [?] there's a point of diminishing returns. Or you could, "I'm gonna do 100 queries of, you know, SELECT field FROM WHERE id=x", which is a very trivial query. Oddly enough, I agree with you, I have always tried to defer to the side of try to do fewer queries, but what we found with some of the LINQ stuff, it's not that it does too many queries, it does very simplistic, small queries and that turns out to be OK-ish on StackOverflow. 

Spolsky: Yeah, it's just, you know, I just think technology's changed since 1995. I mean the other thing that I remember is that we couldn't rely on connection pooling. I don't even think we had connection pooling the first time, so every query was a database login and then do the query and then log out.

Atwood: Wow, that sounds really painful.

Spolsky: We lost Robert. Oh Robert, where did you go? How do you get him back?

Atwood: I'll let him back in, hold on.

Spolsky: Oh you're the organiser.

Atwood: Yes, I will bring him back in. I am calling him now. That's OK with all our blah blah blah...

Spolsky: Yeah, he probably just lost interest, probably fell asleep and knocked the phone off the hook. Umm, err, um, ummm.

Atwood: I'm trying to add him, so

Spolsky: And that is why the world is banana shaped


Atwood: Well did you, while I'm doing this, did you want to start with any questions on Meta?

Spolsky: Yes, so basically, the reason we're doing this special podcast even though we're in hiatus and what-not is because we sort of made a big announcement which some of the podcast listeners may have just completely missed if you only listen to the podcast. Which is a couple of pretty major changes in direction under StackExchange or, to use a Dave Winer term, a "corner-turn". Basically what we're going to do in the future is about 45 degrees different than what we did in the past with StackExchange. Now to bring everybody totally up to speed, StackExchange is the white-label version of StackOverflow that allows theoretically anybody to come along and give us a credit card and we'll sell you the software that we use to make StackOverflow, usually on a hosted basis where we host it for you and you can make any kind of community you want in exchange for a small monthly fee. And what we found is that that worked surprisingly well in a couple - well not surprisingly - that worked well in a couple of dozen instances where it created dynamic and awesome sites, but it was just not really working you couldn't really say. You know, I don't think we're happy with the growth and penetration that we were getting with those few communities that were getting created on the StackExchange model. And so, basically, the corner turn was this: first of all, we're going to stop charging for it, so, you know, originally the price started at $129/month and we just sort of decided that that kind of makes sense when you compare it to other software-as-a-service-type things. I dunno, it's kind of expensive, but it's sort of what we estimated it would cost. And we're going to stopcharging for it, and that makes it much easier to create communities. And then, simultaneously, instead of just sort of letting individual entrepreneurs create communities, we're going to let the communities create the communities. So we're trying to set up a process that almost feels like a democratic process in some ways that people vote for communities that they want to see created and then we'll create them. The difference is that we'll own them, so a bunch of the people that were involved in StackOverflow 1.0 basically, had an entrepreneurial bent to create little businesses, and we'll pretty much allow them to continue as long as they have, you know, some level of traffic and as long as, you know, we can continue to do so. 

Atwood: Well, can I interrupt? 

Spolsky: Yeh

Atwood: So, let's clarify. One question that came up, you know, is the concept of ownership and whether we're going to do this revenue-sharing thing. 

[12:17 onwards]

Spolskyedit me!

Atwoodedit me!

Cartaino: edit me!

Last Modified: 3/22/2016 2:21 AM

You can subscribe to this wiki article using an RSS feed reader.