hehheh
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.
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.
Speaking personally, when I find user-hostile content, I simply leave the page/close the window/throw away the magazine. I don't feel entitled to have the content in any way.
However, I do feel entitled to make an appeal to content producers that they try to come up with a way to make their content less hostile. It's just an appeal, though, and they are absolutely free to ignore it.
One thing I've noticed, that drives me crazy, is people demanding more information in response to a question, without any intention of using that information to help find an answer. Their whole goal is to score points for asking more details. I don't mean to suggest that more details aren't useful, only that it isn't helpful in any way to ask for more information if you don't intend to follow up. (Perhaps that could be improved by allowing those sorts of requests to be sent privately, and without any chance of generating points?)
[1] https://ucr.fbi.gov/crime-in-the-u.s/2015/crime-in-the-u.s.-...
You'd need a few other things:
8. Floor count
9. Size and location of the bedrooms, bathrooms, kitchen
10. In-unit laundry (mostly for condos)
11. Proximity to neighbors
12. Existing tree coverage and other landscaping
13. Proximity to trails, transit, and other mostly-fixed landmarks
... I'm sure I'm missing many more.
As for the assertion that "regulations are not bad, it's needless regulations that are bad" -- the argument sort of falls flat without specifics. The argument can be boiled down to "good things are good, bad things are bad."
* Optionally show thread replies in-line with chat, as they come in, just like regular chat but with some special annotation to indicate they're part of a thread.
* Allow the user to collapse a thread so they no longer see it in-line.
* Auto-close threads after they're idle for more than 1 hour (or some site-policy-configurable timespan).
* Allow the user to navigate between threads using only their keyboard.
As they are now, I think threads are bad for business. They hide useful information away and slow conversation (responses dragged out because they're no longer in your face).
I wonder why Garadget would want to let Amazon process the refund, anyway. It seems like that's got to count against them in some analytics somewhere.
'course, here I am doing the judging now.
The APIs are not great. Some of it is down to poor naming, for example:
The callback you'd use on a CheckBox is called `OnCheckedChangeListener.onCheckedChanged(view, boolean)` (or something) but it is called whether or not the check state actually changed (e.g. if you call `setChecked(true)` and it's already checked you'll get the callback anyway). This is an issue that plagues the APIs in other places like `OnLayoutChangeListener` and `TextWatcher.OnTextChanged`
The fragment lifecycle is incredibly complex to the point that many people advocate against using it -- I'm one of them. It's like someone decided to try to solve every problem ever without asking the real users (devs) what they thought was wrong.
But the worst thing about it, bar none, is just how long it takes to build and run an app. We're talking 1.5-2 minutes. Everyone has their pet idea for reducing the build/test cycle but they provide marginal benefits at best and don't offer up concrete examples with concrete data (e.g. "I am running this gradle command for this github project on this computer and am measuring it this way, and here are my results"). I've spent weeks of time, scattered over the years, trying to figure out a way to reduce this to something more reasonable like 5 seconds, but to no avail.
My best guess is that other people are working on tiny toy apps or are just building the default project and then proclaiming that I must be mistaken, I must be doing something wrong for my build (of a reasonable sized app) to be as slow as it is.
I'm not sure what I'll do instead. I've been reading a bunch of stuff folks have written about the subject, but most people are focused on going in to management or QA or whatever. I think I'd just like "out". My brain ain't what it used to be and I'd rather quit than be fired, if you get my meaning.
I don't have an answer yet. I half-joke about becoming an Amazon Flex driver.
I keep hoping that Google will figure out a solution to that (restrict access to Play Services, say). Until then, I guess I'll continue targeting API 16.