Because we believe all traffic on the web should be treated equally, Stack Overflow will join some of your other favorite sites from around the web including Netflix, GitHub, Reddit, and Amazon on July 12 for a day of action supporting net neutrality.
June 30, 2017 • By Josh Heyer • In Announcements, Community, Company
June 15, 2015 • By Josh Heyer • In Announcements, Community, Company, Stackoverflow
Long-suffering readers may have noticed that, as we’ve expanded Stack Overflow into strange and exciting territories, we always start by hiring a new community manager. These intrepid souls act as emulsifiers, enabling and promoting communication between the company and the growing community. This role is just as critical for our 140+ English-language sites, where our small team works to ensure that requests and concerns are addressed in a timely fashion (6-8 weeks, give or take). Whenever possible, community managers are hired from within the community itself – after all, who knows its needs better than someone who has been a part of it?
October 07, 2014 • By Josh Heyer • In Announcements, Community, Company, Design, Stackexchange
We rolled out three new badges last week!
July 23, 2014 • By Josh Heyer • In Background, Community, Company
As Stack Exchange continues to expand to serve new audiences, we’re constantly on the lookout for folks who can take the principles and practices we all hold dear and communicate them effectively to the folks who would otherwise find them strange and difficult. I’m happy to announce we’ve found another of these rare specimens in the form of Joshua Maciel:
April 08, 2014 • By Josh Heyer • In Announcements, Background, Community, Company
Protected status is an often-overlooked feature of Stack Exchange. It’s based loosely on Wikipedia’s semi-protection, and like that tool is meant to be a reaction to persistent abuse from anonymous or unproven participants: when a page attracts a lot of noise or vandalism from outside the community, Protecting it reduces the amount of clean-up needed later on.