Live data from Hacker News

Stack Overflow reducing headcount by 20%

twitter.com

111–120 of 209 posts

Re: Stack Overflow reducing headcount by 20%

#111
post #106
post #99

Earlier quoted context omitted.

Their Q&A site was vastly better than what existed at the time, and that's how they won the market. Now, though, it is full of people looking for quick points (as you suggest) -- people that think that the original poster was asking for someone to search Google for 'em -- and I'm convinced that the truly helpful people have moved just given up. One thing I've noticed, that drives me crazy, is people demanding more in…

I suspect there's a mismatch between what you expect Stack Overflow to be and what the other users expect it to be. From the tour ( https://stackoverflow.com/tour ): > With your help, we're working together to build a library of detailed answers to every question about programming. The "build a library" being the key part. Vague questions aren't that useful in building the library in particular because lacking the ne…

> Vague questions aren't that useful in building the library in particular because lacking the necessary information, they can have too many unhelpful answers.

If that is truly their goal (and I don't doubt that it's at least a hope) then they should go ahead and remove all the vague questions from their database, or at least flag them so they don't show up in web searches. After all, who's using Google to find unsolved, vague problems?

> No one gets points for comments. At all. The voting on comments is purely for visibility ranking of helpful and constructive aspects to the post they are on... and nothing else. No points.

I see. I didn't realize that. They do get the number but I guess it doesn't "persist" throughout the site. Good to know. Though, then I guess I don't understand what their motivation is to respond with useless comments.

> Instead a comment asking "what version of C++ are you using" up front to make sure that the person asking the question gets the correct answer rather than something that is unhelpful.

That's OK, I guess, but it seems to be counter to the idea of building a library. Rather than have a set of answers that may address the question for various versions of C++, you have a question and zero answers (because the person asking for details disappeared). That's the reality, anyway.

In any case, it wouldn't even have to be a private message. Simply having a "needs more detail" checkbox that hides the question (from Google et al) until the detail is added would be enough to improve the SO experience.

Re: Stack Overflow reducing headcount by 20%

#112
post #111
post #106

Earlier quoted context omitted.

I suspect there's a mismatch between what you expect Stack Overflow to be and what the other users expect it to be. From the tour ( https://stackoverflow.com/tour ): > With your help, we're working together to build a library of detailed answers to every question about programming. The "build a library" being the key part. Vague questions aren't that useful in building the library in particular because lacking the ne…

> Vague questions aren't that useful in building the library in particular because lacking the necessary information, they can have too many unhelpful answers. If that is truly their goal (and I don't doubt that it's at least a hope) then they should go ahead and remove all the vague questions from their database, or at least flag them so they don't show up in web searches. After all, who's using Google to find unsol…

There have been efforts to remove vague questions. There is a lot of them. Stack Overflow corporate tends to leave that to the community moderation... which is a bit under powered. Until recently, the elected moderator team tended to be on the preservationist side. As to removing from search? https://meta.stackoverflow.com/questions/316881/ - remember that Stack Overflow monetization is driven by views. Deleting those vague questions that people search for (they do) that happen to have a lot of views and are locked ends up as a - on the balance sheet.

Reputation changes happen from: * Upvote on a question you asked (+5) * Upvote on an answer your provided (+10) * Accepted answer you provided (+15) * Accepted edit (+2) * Down vote on a question you asked (-2) * Down vote on an answer you provided (-2) * Down vote you gave on an answer (-1); yes down voting other peoples answers costs you points. * Receiving a bounty (+varies) * Giving a bounty (-varies)

Thats it. Nothing about comments. Nothing about closing questions.

The comments aren't necessary useless. They are often trying to help the person asking the question write a better question that can get a better answer. If the comment truly is useless, it should be flagged to be removed (and that won't give or cost anyone any points).

Guessing at the answer isn't that helpful. You've got no idea if it solved the problem or not. The next person to find it with search won't know if it solved the problem or not either. So instead of one question with an answer that did, you've got a question that has a dozen guesses... and you've got to go through and figure out which one works for you in your environment. Might as well have searched a forum and paged through all the guesses there.

Questions that don't have any answers eventually get removed by the system. https://meta.stackexchange.com/a/92006 describes the criteria.

> If the question is more than 30 days old, and ... > has −1 or lower score > has no answers > is not locked

> If the question is more than 365 days old, and ... > has a score of 0 or less, or a score of 1 or less in case of deleted owner > has no answers > is not locked > has view count has 1 or 0 comments

The "needs more detail" is often part of the close reason. The question is closed not as a "you did bad" but rather as a "don't try to guess at an answer until this is cleared up"

> Questions seeking debugging help ("why isn't this code working?") must include the desired behavior, a specific problem or error, and the shortest code necessary to reproduce it in the question itself. Questions without a clear problem statement are not useful to other readers. See: How to create a Minimal, Complete, and Verifiable example.

> Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

The hides from google, again, is the "this is how SO makes its advertising impression money." The reason given often is the "breaks the internet." If people linked to the closed question from outside that link becomes a 404. I'm skeptical on that being the only reason as I noted the advertising impression dollars there. I personally believe that maintaining poor quality material, no matter how many people link to it, is damaging to the brand and sets a poor example for what people asking questions expect. And thus, when they do catch the eye of someone who has an Atwoodian (quality above all else, delete the stuff that doesn't contribute) philosophy of quality on the site, it becomes a poor user experience for everyone involved. And as Jeff isn't there and Joel is CEO, the emphasis is different.

I say Atwoodian there - thats following the call of:

> It is by programmers, for programmers, with the ultimate intent of collectively increasing the sum total of good programming knowledge in the world. No matter what programming language you use, or what operating system you call home. Better programming is our goal.

The Spolskyians are following the call of:

> What kind of questions are appropriate? Well, thanks to the tagging system, we can be rather broad with that. As long as questions are appropriately tagged, I think it’s okay to be off topic as long as what you’re asking about is of interest to people who make software. But it does have to be a question. Stack Overflow isn’t a good place for imponderables, or public service announcements, or vague complaints, or storytelling.

Its shifted a bit from those original calls to people to contribute... but you can see a profound difference in the emphasis between those different calls for contributors. Then give https://stackoverflow.blog/2011/02/22/are-some-questions-too... a read and look at the editor history of https://stackoverflow.com/posts/1003841/revisions

The thing I'm trying to say there is the "why don't these questions get hidden from google" gets an "its complicated" and goes to the top of the company and its founder about what is appropriate for the site and not. Its not something easily done or decided.

Re: Stack Overflow reducing headcount by 20%

#113
Surprised no one has mentioned StackOverflow Docs, which was recently shut down as a failure. I unfortunately panned it at launch but it seems they devoted significant resources to the dead product.

StackOverflow Sunsetting Documentation:

https://news.ycombinator.com/item?id=14917765

Why I think they targeted the wrong market:

https://news.ycombinator.com/item?id=12399438

tl;dr:

- it doesn't make sense to donate open-source docs to an offsite corporate service that might shut down

- also, the very common complaint that SO has poor moderation, groupthink doesn't work for docs like it does for one-topic answers

Re: Stack Overflow reducing headcount by 20%

#114
post #43

Earlier quoted context omitted.

Depends on country too. In EU our work laws regulate how your employee may be laid off. My country (poland) says that employee has to be notified about termination: - week ahead if he or she was employed for less than month - month ahead if he or she was employed for less than three years - three months ahead if he or she was employed for more than three years This goes both ways however, as employee has to notify hi…

Same in France and the majority of EU countries.

Three months seems like way too long to know you're being laid off but I guess maybe the purpose is that it gives you time to find new work?

In the US, it's just assumed that the ex-employee will be as malicious as possible and so it's best to get rid of them fast as possible.

Re: Stack Overflow reducing headcount by 20%

#115
post #107

Earlier quoted context omitted.

I've never heard of a company giving advanced notice of layoffs. Its always just an email the morning of.

http://www.edd.ca.gov/jobs_and_training/Layoff_Services_WARN... > Per Chapter 4, Part 4, Sections 1400-1408 of the Labor Code, WARN protects employees, their families, and communities by requiring that employers give a 60-day notice to the affected employees and both state and local representatives prior to a plant closing or mass layoff. Advance The layoff that I was part of in '09 in California (Netapp, ~500 employ…

Interesting. Company I used to work for reduced their LA office to a handful of people after laying off 2/3 of its workers to move operations to Vancouver. Everyone was considered 'contract' despite being on W2s so not sure. I think we did get a notice but not months to look for new work. I had a week.

Re: Stack Overflow reducing headcount by 20%

#116
post #39

Earlier quoted context omitted.

Usually you will get at least a 4 week notice in Germany and this increases to up to 7 months when you worked for more than 20 years for the company. That you get fired effective immediately usually only happen if you really fucked something up.

The US has much weaker employee protections. Aside from workers in unions and certain protected scenarios, layoffs usually occur with zero notice. (And, often, when associated with public bad financial returns, shortly after management denies any layoffs are coming.)

The WARN act is part of US labor law. https://en.wikipedia.org/wiki/Worker_Adjustment_and_Retraini...

For larger companies with layoffs beyond a threshold, they employer must give 60 days notice. I think they can instead give 60 days severance.

Re: Stack Overflow reducing headcount by 20%

#117
post #112
post #111

Earlier quoted context omitted.

> Vague questions aren't that useful in building the library in particular because lacking the necessary information, they can have too many unhelpful answers. If that is truly their goal (and I don't doubt that it's at least a hope) then they should go ahead and remove all the vague questions from their database, or at least flag them so they don't show up in web searches. After all, who's using Google to find unsol…

There have been efforts to remove vague questions. There is a lot of them. Stack Overflow corporate tends to leave that to the community moderation... which is a bit under powered. Until recently, the elected moderator team tended to be on the preservationist side. As to removing from search? https://meta.stackoverflow.com/questions/316881/ - remember that Stack Overflow monetization is driven by views. Deleting thos…

> Questions without a clear problem statement are not useful to other readers.

I guess this is fundamentally where I disagree with SO's staff and/or moderation team. I occasionally find those questions and their answers very useful, when there are answers, and again more useful than the perhaps ideal, specific, and ignored questions that fill the site. When questions get too specific, the only person that might benefit from the reply is the person that posted the question in the first place. At that point it might as well not be part of a public forum.

My favorite SO pages are those that generate multiple replies with different perspectives, and often different languages or at least libraries. Those questions are admittedly usually vague but I think that given the result (many interesting answers from different people) that is a net positive. You might say that the answers given look like guesses, and that'd be completely fair, but there's still value. Certainly more value than an unanswered question abandoned by both the asker and the one person who expressed a small amount of interest.

I do see the difference you're describing (between Atwoodian and Spolskyians) and I can see the merits in both sides. I'm not satisfied with either, but that's more on me than on SO. In any case, I doubt I'm making any unique or new arguments here. I'm mostly just frustrated with SO and Google in general because I almost never find a solution to my problems.

As a sort of aside:

> The key distinction to make here, in my mind, is that all questions are ultimately in service of the people answering them. That is the audience you need to satisfy if you want to have any hope of creating and sustaining a community of peers learning from each other.

That seems to be how you make a site by and for narcissists, or people otherwise interested in hearing themselves talk. It'd be a different story if the answers were paid, I guess, because at least then the motivation would be something more tangible.

To be honest, I probably would have written SO off entirely if I'd seen this comment earlier.

Re: Stack Overflow reducing headcount by 20%

#118
post #15

Why would you fire people on such a short notice? No need to hand over things? No interest in providing at least some time to look for a new job? EDIT: To clarify that a bit, I am interested in what the upsides are except for possibly saving some money. An orderly shutdown usually seems preferable to me over quickly killing the process, for both sides.

It's start up life, iterating off VC money. Fail fast also means fire fast.

Re: Stack Overflow reducing headcount by 20%

#119
post #76

I tried to hire through them recently. It was a joke of a process. More like the way uaed cars are sold. Don't contact us, we'll contact you. No price displayed, we negotiate that depending on how much you can afford. The sign up system simply didn't work, saying I had already signed up but then the next button simply didn't work. They did get back to me a week later. This completely change my view. I went from wanti…

Indeed is doing a good job at hiring in the tech field. Their Prime product is great (if you live in one of the cities they are running it in).

(Disclaimer: I work @ Indeed, but I've seen friends quickly hired using Prime.)

Re: Stack Overflow reducing headcount by 20%

#120
post #15

Why would you fire people on such a short notice? No need to hand over things? No interest in providing at least some time to look for a new job? EDIT: To clarify that a bit, I am interested in what the upsides are except for possibly saving some money. An orderly shutdown usually seems preferable to me over quickly killing the process, for both sides.

Companies benefit from terminating with zero notice, and subsequently providing money and services to facilitate the employees transitions.

Labor seeks regulations that makes it difficult to be suddenly terminated. The primary downside is that companies are reluctant to hire employees.

Post reply on HN