Stack Overflow Documentation

» see stackoverflow.com/documentation as it lived, on the wayback machine

~ the eulogy ~

stack overflow shipped documentation on 21 july 2016 as the biggest expansion of the site since the original 2008 launch. the pitch on the stack overflow blog was simple. official documentation is incomplete, examples are scattered across blog posts and gists, and the same crowd that had built the world's largest q&a site for programmers could build docs the same way. example-driven, community-edited, reputation-weighted. private beta ran through late 2015 and early 2016 with a few hundred invited tags. the public version launched into a noisy room.

the room got quiet fast. by late 2016 the topics that had been seeded in the first weeks were stale. the easy ones overlapped with what was already on the regular site. the hard ones nobody wanted to write. the system gave you reputation points and edit privileges but it did not give you the small dopamine hit of helping a specific person solve a specific problem at 2am, which is what made the q&a side compulsive. writing the eighty-fifth example of "how to read a file in python" was a chore, not a hit.

on 6 july 2017 stack overflow announced documentation would be sunset. on 8 august 2017 editing was turned off. existing content was archived and slowly removed from search indexes; the urls now redirect or 404 depending on the topic. it was the company's most visible product failure between the 2008 launch and the prosus acquisition in 2021.

i was an engineer who used the regular stack overflow constantly through this whole window. i opened documentation maybe four or five times, hit pages that were just answers in a different layout, and went back to the main site. nothing about it ever felt necessary, which turned out to be the diagnosis.

~ the dossier ~

~ why it did not work ~

the company's own postmortem and the better outside writeups all landed on the same point. documentation does not granularize. an answer is a small reply to a small question, with a clear audience of one followed by everybody else with the same question. documentation is a big object you have to commit to maintaining, with no specific person on the other end. the q&a reputation flywheel needs a recipient to spin. take the recipient out and the wheel stops.

the secondary problem was content overlap. for any popular tag (python, javascript, react) the regular site already had thousands of high-rep answers covering most of the example surface. for unpopular tags, nobody was writing anything in the first place. documentation had no space of its own.

~ what it left ~

it left a useful reminder that q&a sites and docs sites are different products even when the contributors overlap. stack overflow itself kept growing through 2018-2019 then started losing traffic to model-based assistants by 2023. the documentation graveyard sits next to that decline as the earlier signal that the company's expansion options were narrower than the platform looked from the outside. [[stack-overflow-jobs]] would follow with a similar quiet sunset in 2022. each death made the core a little more alone.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »