Topic: stackoverflow

Stack Overflow Careers was announced five years ago with a simple mission statement:

We believe that every professional programmer should have a job they love

To help you find a job you love, we need to match you with the right job at the right time. We do that by helping you create a profile that brings the right employers to you, and by showing you relevant job ads from our job board on Stack Overflow. With over 6,000 companies that advertise on Stack Overflow Careers, we’re getting closer to our goal of having a great job for every developer.

Until today, the job ads that we show on Stack Overflow were pretty stupid: they targeted solely based on location, and ignored all the other information about what you’re looking for and what kind of job it is. They didn’t even care about whether the job was in a technology that you were interested in. So today* we’re launching the first step in showing you jobs that we think are an actual match for you.

_{*If you just ran to a question to see how targeted the jobs were and left disappointed, don’t worry. This feature is just launching today and most employers haven’t had a chance to target their jobs yet. You’ll see the difference over the coming months.}

Developer Types, Tech Ecosystems, and Tech Tags

Many of you will start noticing that the jobs you see aren’t just in your area, but are related to the question you’re viewing, a question you’ve answered, or something you’ve asked about. We’re using this little bit of data, along with the location data we were already using, to predict what type of job you’re more likely to want to apply to. We then do some predictive modeling based on this information to target mobile jobs at mobile devs, front-end web development jobs at front-end devs, and even more complex stuff based on technology stack and specific tags.

It’s difficult to show you an example of a targeted ad. We haven’t changed much about the ad design or even how the job is displayed in the ads. However, we can show you the other side, how the employer is targeting their jobs.

This is all organized into three tiers of targeting criteria:

1. Developer Types: The broadest description of a developer.
2. Technology Ecosystems: A narrower description, best described as tag clusters.  Python includes frameworks like Django and Flask. Cloud (back end) implies knowledge of AWS, Microsoft Azure, Rackspace, etc.
3. Stack Overflow Tags: The most finely-grained descriptor. These draw straight from the top 1,000 most popular tags on Stack Overflow.

It’s really that simple. Once employers fill out a targeting profile for a job, we’ll try and predict which of those jobs you’ll be interested in.

Fine, but these are just ads. Why should I care?

Hopefully this doesn’t change much about how you use Stack Overflow in your daily life. Job ads are only a small part of our page content, but we hope this launch will improve your odds of seeing the right job opportunity at the right time. So far it appears to be working. Initial testing of targeted jobs over the past few months have demonstrated significant progress toward our goal of showing relevant job ads to each developer, as clickthrough rates increased 21-30%. Not bad for a V1!

We also want to let you know exactly how we’re targeting jobs, so our newly created data team will be talking about building out the infrastructure for this project, and all the details of what went into it. You can follow these posts on Kevin Montrose’s blog starting today. Jason Punyon will also be adding to this series later this week and next.

Additionally, if you want to see your personal prediction data, or if you want to disable predictions, you can do that from the user preferences page.

This sounds cool; I want to use it to hire a developer!

If you want more details on how this works for employers, go visit our Stack Overflow Careers blog. If you want to dive right in, you can post a job now and fill out a targeting profile. And if you already have a job running, you can edit it to add targeting for the rest of its run.

That’s it! As always, if you have questions or comments feel free to post on Meta Stack Exchange in the ‘Careers’ tag.

Hi English-language readers! This blog post is not for you; perhaps you’d like a hat instead? No? Well, when last we spoke of creating non-English versions of Stack Overflow, some of you were certain we should’ve gone the easy route and just leveraged a machine translation service instead of creating real sites for real people to use. I humbly invite you to read the rest of this post using the mechanical babelfish of your choice, and see if you think such tools can be relied on for important work…

2008年にStack Overflowが設立された目的は、プログラミングに関する質問の全ての回答をまとめあげ、それらを提供する場を作る事でした。Stack Overflowの誕生以前は、プログラマー自身が自身の貴重な時間を使い、複数のブログ、掲示板やニュースグループで回答を検索した上で、その回答が有効か否かを自分自身でチェックするしかありませんでした。

現在、Stack Overflowは700万個以上の質問をまとめている事で、毎月4,400万人のプログラマーをサポートしています。そしてそのうち60万人以上もの人が日本からアクセスしています。Stack Overflowは英語のサイトにも関わらず、日本のプラグラマーのプログラミング問題を解決する為の必要なツールになってきました。

Stack Overflow日本語版へようこそ

日本には100万人以上のプログラマーがいます。

Stack Overflow日本語版の誕生により今後は、英語と格闘しながらプログラミング問題を解決する必要が無くなります。

2014年12月2日にStack Overflow日本語版のプライベートベータを開始し、1週間で1000人以上のユーザーと100個以上の質問が集まりました。そして今、日本の全てのプログラマーに開放する運びとなりました。Stack Overflow英語版と同じ様に皆様と一緒に日本語でのリソースを作成しましょう。

日本のプログラマーを応援しましょう

これからは日本語でのプログラミングに関する質問や回答の投稿が可能となります。今日から投稿して頂く質問は将来の日本人プログラマーのサポートとなります。日本のプログラミング能力を集結し皆様の知識のレベルアップを図れるチャンスです！

Stack Overflowは皆様のサイトです

Stack Overflowはコミュニティのものです。参加者は投票する事で最も有効な質問や回答を示す事が出来、権限において投稿の編集や管理を行う事も出来ます。そして、コミュニティ内で当サイトの改善案を自由にメタで討議する事ができます。コミュニティは既にリスト質問やリンクのみの回答をどうするべきか討議を開始しています。

当サイトは日本語のプログラミング問題・回答のベストリソースを目指しています。皆様と一緒に作り上げましょう！

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.

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:
   • 10% of the world’s programmers are in China
   • 1.4% of our visits come from China
   • Only 4.8% of our visits come from China, Japan and Korea combined

   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.

   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.

If you can’t read the rest of this post, it’s because I’m not talking to you. Which is a little weird, since I can’t even read this without help from our Brazilian Community Manager, Gabe, who’s been kind enough to help me write this in Portuguese.

Depois de semanas em beta privado, nós temos o prazer de anunciar que hoje vai ao ar o nosso primeiro Stack Overflow internacional. E não se trata de um clone em português do site original, mas sim de uma comunidade completamente nova. Uma comunidade que vai poder decidir como ela quer ser, e como vai poder ajudar os desenvolvedores de língua portuguesa.

Tá esperando o que pra criar sua conta?

Sempre quisemos ajudar o máximo possível de pessoas

Quando lançamos o StackOverflow.com (em inglês), a ideia era ter um lugar onde todos os programadores pudessem resolver problemas juntos.

Queríamos um lugar onde desenvolvedores pudessem compartilhar seu conhecimento, num formato melhor do que os fóruns tradicionais. Queríamos que a melhor resposta tivesse destaque e que fosse fácil encontrá-la, tanto para quem perguntou quanto para alguém que pesquisasse sobre o mesmo assunto no futuro.

Construímos um lugar onde a comunidade pode editar e melhorar os posts, votar na melhor solução e trabalhar em conjunto para chegar na melhor resposta. Nosso objetivo era dar à toda comunidade as ferramentas certas e o poder de colaborar e ajudar uns aos outros.

E deu certo.

O Stack Overflow em Inglês tem hoje mais de 6,5 milhões de perguntas, e mais 8 mil delas são criadas todos os dias. Praticamente todas recebem uma resposta correta, que vem logo abaixo da pergunta.

E é a comunidade quem faz tudo isso acontecer. O conteúdo, a edição e até a moderação é feita pelos próprios usuários. Gratuitamente. Porque eles querem ajudar uns aos outros. Ou mostrar uma solução elegante. Ou retribuir a ajuda que receberam.

Mas é preciso saber falar inglês.

Nós não achávamos que o site em uma só língua seria um problema, afinal a maior parte dos programadores fala inglês, né? As próprias linguagens de programação são em inglês, não é mesmo? Mas nos esquecemos de algo muito importante:

Não estávamos escrevendo um manual técnico. Estávamos construindo uma comunidade.

Demorou um tempo, mas nós finalmente percebemos o que muitos de vocês já sabiam. É muito difícil fazer parte de uma comunidade que, literalmente, não fala sua língua.

Hoje o dia é dos programadores de língua portuguesa!

Agora vocês tem um lugar só seu, para construir do seu jeito. A melhor parte de participar de um site novo é que há um mundo de possibilidades pela frente:

Se você é jovem ainda, amanhã velho será… Então aproveite!

As perguntas básicas – aquelas que um dia atormentaram todo programador – ainda não foram feitas. Você pode escrever a pergunta ou resposta definitiva, que vai ajudar dezenas de milhares de programadores no futuro. (Ah, e não se preocupe se a sua pergunta já está no site em inglês. Vocês vão construir um site justamente para que os desenvolvedores que falam português não precisem mais recorrer ao inglês para aprender coisas novas!)

Você pode ser o que quiser quando crescer.

Apesar do site ser dedicado à problemas de programação, você pode decidir que sua comunidade realmente precisa, assim como aconteceu com o Stack Overflow. Durante o começo do site, sejam mais liberais quanto a perguntas de recomendação de ferramentas ou bibliotecas, perguntas relevantes à administração de sistemas ou outras áreas de TI.

Por enquanto, se tem a ver com programação, pergunte à vontade.

Por que começar com português?

[Nota do tradutor: Porque português é a melhor língua, o Brasil é o melhor país e o Jay não consegue ler o que a gente escreve ;)]

Queríamos começar com uma comunidade que atendesse a dois requisitos:

• Um grande número de desenvolvedores talentosos, em que
• Grande parte deles se sentisse muito mais confortável em falar sua própria língua do que o inglês

Então a escolha foi muito simples. O Brasil conta com uma das maiores e mais fortes comunidades de programação do mundo, e isso sem contar Portugal, Moçambique, Angola e outros países menores que acrescentam ainda mais desenvolvedores talentos a esse grupo.

Esse site é de todos vocês. Vamos construí-lo juntos!

Crie sua conta. Ou faça o tour (e ganhe sua primeira medalha!)