Technology

37719 readers

280 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

347

The Fall of Stack Overflow (observablehq.com)

submitted 1 year ago by [email protected] to c/[email protected]

267 comments fedilink hide all child comments

Over the past one and a half years, Stack Overflow has lost around 50% of its traffic. This decline is similarly reflected in site usage, with approximately a 50% decrease in the number of questions and answers, as well as the number of votes these posts receive.

The charts below show the usage represented by a moving average of 49 days.

What happened?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 19 points 1 year ago* (last edited 1 year ago) (1 children)

A lot of companies won't employ technical writers, who exist to make good, thorough, complete and well-presented documentation... they rather assume their engineers can just write the docs.

And no, no they can't... very few engineers study the principles of effective communication. They may understand things, but they can't explain them.

[–] [email protected] 1 points 1 year ago

That’s fair. At my company we have technical writers for the external docs and internal docs are usually written by whoever has worked on something and got frustrated that nobody in the company could give them a high level overview, and they had to go through the code for a couple hours.

Tbf though, I’ll take docs that aren’t written super well that tell me how things from our internal libraries should be used. Or just comments. I’ll take comments telling me WHY we are doing something.

I don’t expect our internal docs to be MSDN docs. But I like to read an overview of at least the workflow before I jump into updating a large project.