\u003C/a>\n\nOur commitment to the Stack Exchange network is completely unchanged, and we’ll continue to invest in its expansion and growth. SE’s users have built a network of constructive, civil communities of helpers on a previously unheard-of scale, and we’re insanely proud to be a part of it. Here are just a couple of facts to drive home how much you’ve all achieved:\n\n\u003Cul>\n \u003Cli>The network as a whole has more monthly 5-time \u003Cem>posters\u003C/em> than English Wikipedia has 5-time monthly \u003Cem>editors.\u003C/em>\u003C/li>\n \u003Cli>Stack Exchange is the \u003Ca href=\"https://www.quantcast.com/top-sites\">47th most visited website in the US\u003C/a> \u003Cem>without Stack Overflow,\u003C/em> and gets roughly as many US visitors each month as the New York Times.\u003C/li>\n\u003C/ul>\n\nHere’s what one of our investors \u003Ca href=\"https://medium.com/@cdixon/a16z-leads-40m-investment-in-stack-exchange-a84b6c1b9122\">had to say\u003C/a> on the topic:\n\n\u003Cblockquote>I believe Stack Exchange’s growth has now reached escape velocity. Not only will the existing topics continue to grow, but many new topics will emerge, until the network covers every topic that is amenable to objective Q&A. As new generations of people grow up on the internet, old habits — searching through textbooks or how-to books, or asking friends—will fade away.”\n\n --Chris Dixon, Andreessen Horowitz\u003C/blockquote>\n\nYou hear that, books?? We’re coming for you, you filthy tree-based anachronisms.\n\n\u003Ch2>Q: So, why the change?\u003C/h2>\n\n\u003Cstrong>We started with better Q&A for developers.\u003C/strong>\n\nWhen we named the company Stack Exchange, we were \u003Cem>only\u003C/em> making Q&A sites. We’d had great success with Stack Overflow Q&A and we were expanding that engine to serve new topics. So, using the Q&A network’s name for the company made sense. If we’d decided to make one of those lame, corporate hierarchy charts,and for some reason had chosen to ask an untalented child with a crayon to draw it, it would have looked a lot like this:\n\n\u003Ca href=\"https://i.stack.imgur.com/tgyY5.jpg\">\u003Cimg src=\"http://stackoverflow.blog/wp-content/uploads/2017/02/tgyY5.jpg\" alt=\"enter image description here\" />\u003C/a>\n\nAnd just to be clear, Q&A \u003Cem>remains\u003C/em> our core product, and we’ll continue to invest in helping it serve more of the world’s \u003Ca href=\"http://stackoverflow.com/\">developers\u003C/a>, \u003Ca href=\"http://chemistry.stackexchange.com\">chemists\u003C/a>, \u003Ca href=\"https://photo.stackexchange.com/\">photographers\u003C/a> and \u003Ca href=\"http://worldbuilding.stackexchange.com/\">whatever the heck these awesome people are\u003C/a>.\n\n\u003Cstrong>Then, we focused on better \u003Cem>jobs\u003C/em> for developers.\u003C/strong>\n\nIt was pretty obvious that even though developers were scarce, valuable talent, most job boards were still designed for \u003Cem>recruiters’\u003C/em> needs, and were full of fake “exciting new startup!” listings and jobs requiring things like “8 years experience with Swift”. Tired of that nonsense? So were we. So we built \u003Ca href=\"http://careers.stackoverflow.com/why-stack\">Stack Overflow Careers\u003C/a>. Which \u003Cem>totally\u003C/em> effed up my corporate chart structure. But Joel was all,\n\n\u003Cblockquote>“We’re supposed to be \u003Cem>relentlessly\u003C/em> serving devs, not charting dopey crap. Figure it out, or I’ll take your standing desk away, and tell the pastry chef no seconds for you.”\u003C/blockquote>\n\nBut I \u003Cem>still\u003C/em> couldn’t come up with any good spot for Careers, so I just stuck it somewhere random. And since Joel had said \"relentless\" a bunch of times, I added a drawing of Batman, cuz he’s super-relentless and I was a lonely teenager:\n\n\u003Ca href=\"https://i.stack.imgur.com/LG8kA.jpg\">\u003Cimg src=\"http://stackoverflow.blog/wp-content/uploads/2017/02/LG8kA.jpg\" alt=\"enter image description here\" />\u003C/a>\n\n\u003Cstrong>Next up? Better \u003Cem>EVERYTHING\u003C/em> for developers.\u003C/strong>\n\nWhich brings us to today. Now, we \u003Cem>could\u003C/em> just sit on our laurels and reflect on all we’ve achieved. I actually proposed that laurel-sitting plan, but you know how Joel is:\n\n\u003Cblockquote>\"You know when you get to sit on your laurels? When \u003Cem>every\u003C/em> developer problem has been solved. Last week, Carmack Instagramed that that he was eating a crappy sandwich. \u003Cem>YOU ARE FAILING HIM.\u003C/em>\"\u003C/blockquote>\n\nHonestly, some days I worry about Joel, but he’s on to something:\n\n\u003Ch3>Developers have a \u003Cem>lot\u003C/em> of problems.\u003C/h3>\n\nWe got here by focusing on underserved developer needs, and asking the world’s developers to help us solve them. I think that if we’d set out to build the best Q&A platform for \u003Cem>everyone’s needs\u003C/em>, it wouldn’t have helped anyone. By narrowing our focus to a specific group we thought we could help, we were able to create a product \u003Cem>opinionated enough to actually make a difference\u003C/em>.\n\nSo, we’re going to stick with the plan. As we look for new ways to serve our users, we’ll focus on what we know best: solving developer problems. Today, we’re working on our biggest expansion since Stack Overflow launched: Documentation. You can \u003Ca href=\"http://meta.stackoverflow.com/questions/303865/warlords-of-documentation-a-proposed-expansion-of-stack-overflow\">learn more about it here\u003C/a>, or \u003Ca href=\"https://docs.google.com/forms/d/13ynCK-DEy0osod8VIENajnbFJNZxXm1jyeupBrl5v44/viewform\">sign up for the beta\u003C/a>, and be part of building what we think will be our next Big Thing.\n\nI should point out that we fail a lot around here. But wherever we’ve succeeded, it’s come from focusing on how we could better serve devs’ needs. And when that success looked transferable, we passed it along to the rest of the world. So, we’re gonna run with that, and hope you all keep on running with us.\n\nHere’s what that crayon wielding kid thinks we look like today:\n\n\u003Ca href=\"https://i.stack.imgur.com/jUGxZ.jpg\">\u003Cimg src=\"http://stackoverflow.blog/wp-content/uploads/2017/02/jUGxZ.jpg\" alt=\"enter image description here\" />\u003C/a>\n\nDo I hope to see more multi-colored, (poorly-drawn) networks spring up around some of our other dev products? Hell yeah. Will they? Beats me. But as always, we’re counting on you to help us figure it all out.\n\n\u003Ch2>Didn’t you say something about the logo?\u003C/h2>\n\nOh - right. With the exception of a few minor tweaks, the Stack Overflow logo that you know and love has been essentially unchanged since we paid \u003Ca href=\"http://99designs.com/logo-design/contests/logo-stackoverflow-6774/entries\">$512 for it in in a 99 Designs contest\u003C/a> back when that was a \u003Cem>lot\u003C/em> of money for us. We thought it was pretty awesome then, and it’s still pretty awesome now. So, the design team didn’t change much, and just made a simple, clean update to the existing logo. Next week, they’ll share how it fits into a new style guide we’ll be using to help us standardize our visuals and save valuable design cycles downstream.\n\nBut for now, we were inspired by Google’s video explaining how they arrived at their new logo concept of “kindergarten letters, most of which are actually aligned correctly.” So we made a short video. While ours doesn’t include the phrase, “…and just the right soupçon of whimsy” nearly as much as theirs did, I think it does a nice job conveying exactly how ours got changed.\n\n\u003Ciframe width=\"560\" height=\"315\" src=\"https://www.youtube.com/embed/uipTZ2re4Uk\" frameborder=\"0\" allowfullscreen>\u003C/iframe>\n\n(Film by our own Benjamin Dumke-von der Ehe, aka \u003Ca href=\"http://meta.stackexchange.com/users/115866/balpha?tab=profile\">balpha\u003C/a>, music by \u003Ca href=\"https://www.jamendo.com/en/artist/340121/zero-project\">Zero Project\u003C/a>)\n\n\u003Ch3>We are Stack Overflow. And we’d be nothing without all of you.\u003C/h3>","html","2015-09-15T12:00:00.000Z",{"current":731},"were-changing-our-name-back-to-stack-overflow",[733,741],{"_createdAt":734,"_id":735,"_rev":736,"_type":737,"_updatedAt":734,"slug":738,"title":740},"2023-05-23T16:43:21Z","wp-tagcat-announcements","9HpbCsT2tq0xwozQfkc4ih","blogTag",{"current":739},"announcements","Announcements",{"_createdAt":734,"_id":742,"_rev":736,"_type":737,"_updatedAt":734,"slug":743,"title":744},"wp-tagcat-company",{"current":217},"Company","We're Changing Our Name (Back) to Stack Overflow",[747,753,759,761],{"_id":748,"publishedAt":749,"slug":750,"sponsored":12,"title":752},"1b0bdf8c-5558-4631-80ca-40cb8e54b571","2025-08-21T14:00:25.054Z",{"_type":10,"current":751},"research-roadmap-update-august-2025","Research roadmap update, August 2025",{"_id":754,"publishedAt":755,"slug":756,"sponsored":12,"title":758},"5ff6f77f-c459-4080-b0fa-4091583af1ac","2025-08-20T14:00:00.000Z",{"_type":10,"current":757},"documents-the-architect-s-programming-language","Documents: The architect’s programming language",{"_id":16,"publishedAt":17,"slug":760,"sponsored":12,"title":20},{"_type":10,"current":19},{"_id":762,"publishedAt":763,"slug":764,"sponsored":12,"title":766},"f0807820-02d7-4fc5-845f-3d76514b81c0","2025-08-11T16:00:00.000Z",{"_type":10,"current":765},"renewing-chat-on-stack-overflow","Renewing Chat on Stack Overflow ",{"count":107,"lastTimestamp":768},"2023-05-25T09:45:54Z",["Reactive",770],{"$sarticleModal":725},["Set"],["ShallowReactive",773],{"sanity-2pRNqsEOd_oIDVWfYgSvBoRU1x6LS50_xdNrl3jwyeM":-1,"sanity-comment-wp-post-5158-1756057405683":-1},"/2015/09/15/were-changing-our-name-back-to-stack-overflow"]