site title

Podcast #56 – Green or Red Curae

posted under by on 03-17-14 8

Welcome to the Stack Exchange Podcast #56 recorded on Thursday, March 6th 2014, aka the 4th of Adar II 5774, aka the second day of Lent. Today’s podcast is sponsored by Patent Trolls of America. Today’s guest is Micah Siegel, Senior Patent Advisor at Stack Exchange and Professor Emeritus at Stanford.

But first, Community Milestones!

  • We’ve already talked at length about The Workplace, but it should be noted that the Workplace community has just graduated. They are now a fully-fledged site, so go check out their design!
  • Arduino is our newest public beta site. (An Arduino is a tiny little computer board thing, according to Jay.) We’ve tried it in the past and didn’t have enough activity, but this iteration is looking much stronger and we’re excited to see where it will go. Also, March 29th is Arduino Day.
  • At long, long last, Personal Finance & Money has graduated. We love money! Longtime beleaguered designer Jin finally has assistance on his design team, so we are working through the backlog of graduated site designs.

To commemorate Money’s graduation, we’ve made it Community of the Week. Here are some of the cool questions we discussed:

This site grew out of an SE 1.0 site on the same topic, and it’s therefore one of our oldest sites. Check it out!

Next up, we have New Features. Or, we don’t, because we haven’t done anything, and David is demoted. Just kidding: we do!

Okay! Let’s talk patents! (Jay loves them, but David says they’re the worst.) It’s been a year since we started the Ask Patents project. Joel walks us through why we got into this area in the first place, and we fixed the problem. Done. Solved! (Kinda.) It’s confusing, because code is both copyrightable and patentable. About 7% of the patent applications submitted to the USPTO are what we call problematic. We decided to pick out the ones we are most concerned about and post them on the site for our communities to peruse and choose prior art. Micah talks through how we chose the patent applications to post, and how it’s been going. (Fun fact: we are the first entity to get a YouTube video accepted as prior art!)

We came up with a hack about six months ago to help us make this process scale. Instead of filling out the janky confusing form, we simply started emailing the relevant Ask Patents link directly to the patent examiner. Magic!

So is it working? We’ve proven as far as we can tell that if we target a bad application and put enough eyes from Stack Overflow on it, we’ll get good prior art. We know how all of the numbers break down: exactly how many people on Stack Overflow have to see the bad software patent in order for us to get enough prior art that enough of it will be good enough prior art to trigger an email to the patent examiner.

What can people do right now if they want to make a difference? Go find some prior art requests and post prior art to help us destroy some patents. (Also, you can follow Ask Patents on Twitter.)

Micah is consulting for a few other companies on patent issues, so you can contact him if your company wants to pick his brain. He knows a lot about the current Supreme Court case that might outlaw software patents altogether (but not for a long time).

Thanks for listening to Stack Exchange Podcast #56, sponsored by the Patent Trolls of America. See you next time!

8 comments

Your communities list is now customizable

posted under by on 03-03-14 17

A few months ago, we rolled out a new top bar for all of the Stack Exchange communities. The mission was consistency: Every community gets the same Stack Exchange brand at the top, the same navigation between sites, and the same live updates about new inbox items and reputation changes

But we realize that not everybody uses Stack Exchange the same way. Some people focus on one community, others participate in several, and more than a few spend a lot of time lurking now that we have 116 different sites to choose from.

That’s why, as promised, we have made the “Your communities” section of the Stack Exchange drop-down fully customizable so you can keep all of your favorite communities right at the top.

Edit link

Here’s how it works:

Customizing this list is completely optional. If you do nothing, you will keep the defaults: your top five communities by reputation.

Edit mode

But click the edit button and the default rules no longer apply. Instead, you can:

  1. Add a community to the list by typing the name and clicking Add
  2. Repeat #1 to add as many as you want
  3. Change the order of communities in the list by clicking and dragging
  4. Click the Save button to apply your changes!


You can reset the list to the default at any time, so try it out! Then drop by the Meta post to share your thoughts and feedback.

 

17 comments

Podcast #55 – Don’t Call It A Comeback

posted under by on 02-24-14 12

Welcome to Stack Exchange Podcast #55, recorded on Friday Thursday the 13th with your hosts Joel Spolsky, David Fullerton, and Jay Hanlon! Today’s episode is brought to you by the city of Sochi, Russia.

  • It’s been a long time since we last recorded, so we have a lot to talk about, and we’re going to skip most of it. First we’re going to talk about all our brand new sites, so Joel learn about them for the first time.
    • Pets is a site for (you guessed it) pet owners to wonder why their cats like to watch them making the bed. Also, we already talked about this site. Moving on!
    • We also launched Italian, which is very high quality but unfortunately very slow so far.
    • Jay thought Ebooks would be awful, but it has turned out to be extremely high quality and high engagement.
    • Hooray, beer! Our new Beer site is somehow different from Homebrew, so Joel quits.
    • We launched a Relationships & Dating site, but we broke up with it pretty quickly because it generated too many bad “commitment” jokes (and because the topic was a hard fit for our engine).
    • We launched a site for software recommendations. And discussed it at length. The good parts version: it’s going much better than expected.
    • We almost forgot to talk about Aviation! It launched a while back, and it is a slam dunk for our engine.
  • It’s time for our Site of the Week! (This week was apparently four months long.) Let’s talk about Code Golf. It’s a site for code golf (unsurprisingly!). Links discussed:
  • We already talked at length about the new topbar, but it has bred some interesting changes to other areas of our pages. For example: when we moved Hot Questions out of the MultiCollider and into the sidebar, Code Golf started getting huge boosts on their most interesting questions (as did other sites with broadly interesting topics). Code Golf is seeing 11-15% more answers due to the traffic coming in from other sites via the Hot Questions sidebar. Neat!
  • So! Let’s talk about our most exciting new site: Stack Overflow em Português. Localizing our codebase was a dream of ours for a long time, and we finally did it. It’s got 1304 perguntas at the time of recording this podcast. (If you want to know more about why we launched a non-English site, check out Jay’s blog post.) The public beta so far is one of our most successful launches ever.
  • Also, you can go download our Android app or sign up to test our iOS app.

Thanks for joining us for Stack Exchange Podcast #55, sponsored by the city of Sochi, Russia – don’t forget to visit the Friendship Tree. See you next time!

12 comments

2013 Stack Overflow User Survey Results

posted under by on 02-19-14 45

In 2013, our Stack Overflow community grew from 21.5 million to 26.9 million monthly visitors from 242 countries around the world. We’re doing a lot to keep growing with the community — we now have localized versions of Careers 2.0 for French and German audiences, we’re developing iOS and Android mobile apps for our entire network, and our first ever localized version of Stack Overflow with the Portuguese site currently in beta. As a way for us to make sure we’re doing the most for our users and community on Stack Overflow, we conduct a survey every year to see what you’re up to, how you’re using our site and what else is on your mind. This year, we analyzed a survey sample of 7,500 responses from 96 countries. As a thank you for the time you spent filling it out, we donated an additional $12,000 to our Stack Exchange Charities.

Observations

This is the second year we’re calling out mobile, and yes mobile is still growing.

While only 7.9% of you classified your occupation as a Mobile Application Developer, the majority of respondents (51.5%!) said that their company has a native mobile app. This is an increase from 2012 when 48.2% of respondents had a mobile app.

Android continues to climb while iPhone declines

Not only is the Android Phone the most popular mobile device with 63.8% of respondents saying they have one, the most popular native mobile platform supported is an Android Phone app with 39.5%. The iPhone lost more traction with developers this year with 30.7% of respondents saying they own an iPhone compared to 35.2% in 2012.

Working Remotely

As our Stack Exchange team is growing and we have more employees working remote, we added a number of questions about remote work. While only 10.6% of respondents said they are full-time remote, 63.9% of total respondents say they work remotely at least occasionally.

Here’s a special infographic to sum up our survey findings. If you’d like to do your own analysis you can download the survey results.

developers_final

45 comments

Can’t We All be Reasonable and Speak English?

Two weeks ago, we announced the public launch of Stack Overflow in Portuguese, our first-ever non-English Stack Overflow community. Which raises one very obvious question:

Have we lost our minds?

Wasn’t the whole point of Stack Overflow to aggregate as much developer knowledge as possible in one place? To get all the potential solutions together, and provide one canonical set of answers?

We are aware that, “Let’s all try speaking speaking different languages!” hasn’t always worked out for the best.

Yup. When we set out to “collectively increase the sum total of good programming knowledge in the world,” a big part of the plan was de-fragmenting information previously spread across myriad books, sites, and your brains. It’s why we mark things as duplicates – we want all the precious gems of knowledge stored in the same cave of wonders.

So know this: we are at least as worried about fragmentation as you are. And we have a plan:

Eventually, all of you are going to have to learn Portuguese.

Okay, not really. But, given that one of our core goals was knowledge aggregation, it does seem just a little bit crazypants to start launching sites in new languages, assuming that one very important fact is true:

Assumption: All of the serious developers in the world are highly proficient in English.

Which… actually sounds plausible. But it’s wrong.

  1. Not every developer in the world speaks English. Just reading the comments from our announcement, you’ll see multiple readers sharing that they or their colleagues (and one dad) couldn’t participate on SO due to language constraints. But data beat anecdotes. We don’t have recent numbers for Brazil and Portugal, but we do for China, and they illustrate the same point:

    So, if the data tell us that we’re getting roughly 80% less activity from Asia than we should in the absence of language constraints, why does it feel so obvious that all serious programmers speak English?  This may help:

    Quick – name any famous developer who doesn’t write well in English.

    I couldn’t.  I can name over a dozen famous English-speaking coders. But even if you frequent all the hacker sites and conferences, how many devs have you met who aren’t solid in English? Roughly none, right?

    There’s just one problem. Try this:

    Without Googling, name any famous developer from Japan. Or China. Or Russia.

    Again, I couldn’t. Well, I came up with Shigeru Miyamoto. But he’s apparently a designer. I couldn’t name even one. Not like I can name Carmack or Stallman, or Hopper, or even “DHH.” (Does DHH have an actual name? I personally imagine him as a very handsome, talented, fast-driving set of initials. But I digress.)

    Is it plausible that there aren’t any devs good enough to be famous from those countries? Nope. Here’s what’s happening:

    It’s easy to assume that there aren’t any devs who can’t speak English because I never see any. But I never see any because I’m hanging around places where devs go to talk to each other in English.

    The startling truth is this:

    On the internet, If you don’t speak English, you’re completely invisible to me.

    I also assumed that since developers have to learn English-like syntax, they must speak English. Which is a bit like assuming that because I can order Uni, Hamachi, and Aji by their Japanese names, I could probably toss back some sake with Morimoto and discuss knife techniques in Japanese. Even when programming languages use words like “if” or “function,” they’re just terms to memorize, and don’t always even mean the same thing in English that they do in programming.

  2. It’s almost impossible to feel like part of a community if you’re not highly proficient in the language. Even non-native speakers who are fluent enough to read posts in their second or third languages often aren’t comfortable enough to write in them.

    I imagine myself at a professional meetup where everyone is speaking French (which I studied through college). How many jokes would I tell? How many would I even understand? Sure, I can function, and understand all the words, but I don’t feel like I belong to the group.

    Don’t get me wrong – some of our best users aren’t native English speakers, but they’re in that rare group who have achieved a far higher mastery of a language than their peers. When I hear,

    “Well, I didn’t need a site like this – English is my third language, and I’m in the top 1% on Stack Overflow!”

    I think:

    “Yes, that makes sense. You are insanely good at two difficult, language-based things. Most people will find both of them to be a lot more challenging than you did.”

    The truth is, by requiring fluency in English, we’re shutting out of a lot of developers who may know enough English to read it but not enough to feel comfortable participating.

  3. Requiring that all aspiring devs “just go learn English” first isn’t who we want to be.
    No child should be denied their chance to revolutionize tomorrow's input technologies.

    No child should be denied their chance to revolutionize tomorrow’s input technologies.

    Even if I believed that every programmer must eventually master English, it still wouldn’t make any sense to make them do it first. I believe that everyone – everyone – who can really fall in love with programming should get a chance to. So pre-filtering for the ones willing to learn a foreign freaking language before they first sit down with a code editor to see if it lights some spark in them just feels wrong.Think of the children. The children!! Okay, last quiz, just for the native English speakers:

    How old were you when you first realized you could type things on a keyboard and control machines? Great. Now, at that age, were you proficient enough in another language to have learned to code without any English?

    When I tell someone I work at Stack Exchange, my absolute favorite response is:

    “I basically learned to code from posts I found on Stack Overflow”

    We want that for every young programmer. Not just the ones lucky enough to be born somewhere that English gets taught in grammar school.

Okay, that all makes some sense. But why Portuguese?

To be clear, we still don’t think there needs to be a Stack Overflow in every language. We do want as much centralization as possible, and we know that devs who have mastered English will mostly keep going to the English site, since it has the most critical mass. Just like we want them to. So, you won’t need to learn new languages to find good answers – we expect almost every question asked on the Portuguese site to also be asked (and answered) on the English site.

We’re really only considering launching sites in languages that:

  • Have large, strong communities of high-talent developers, where
  • A meaningful percent of them aren’t comfortable enough to participate in an English-only community

That probably limits the list of potential candidates to Mandarin, Japanese, Portuguese, Russian, Turkish, and Spanish. From there, Portuguese was a no-brainer. The developer community in Brazil is awesome, and growing fast. And we wanted to start with a language with a similar alphabet, to minimize the localization work.

And it’s worth a shot. We’ve learned that it’s easier to just watch the future than to try to predict it. So we’re big on just trying stuff out (assuming it can’t break our other stuff). And we’re huge on getting stuff crazy-wrong, refusing to admit it, and instead doubling down on our wrong-minded idea, while nodding crazily er… admitting we made a mistake, and reversing course. So, given the number of user requests, we figured, “why not give it a it a try?” We’re committed to supporting one or two languages and seeing how they develop before we push any further.

And so far, it’s an incredible success. Despite an audience limited to portuguese-speaking devs, the site’s activity in its first week was higher than all but 4 out of 120 sites we’ve launched to date, including the original trilogy.

More importantly, people who couldn’t ask questions are asking them, and getting great answers. When in doubt, we want to err on the side of helping more people. If just one little girl in Brazil sticks with programming because an answer on this site helped her finish her first project, well… that’s not good enough!  I want to help thousands of them. And the boys, too.

Still, it’s a good start.

197 comments