Meta Stack Exchange is a question and answer site for meta-discussion of the Stack Exchange family of Q&A websites. It only takes a minute to sign up.
Sign up to join this community
When you are looking around for questions to answer, how do you find them? What is your answering "workflow"?
I've been opening up a tab with the newest questions from some language, and then checking it every time I see new questions pop up in the tab title. I feel like there's got to be a better approach, both for my rep and for the community (in terms of looking for things to edit/flag/retag/idk).
So, how do you approach it?
You can't spend all your time answering questions. Completing other tasks on the site (and there's always things to be done) is another great way to contribute to the community and carry on learning. To name a couple of my personal favourites,
All of these things contribute to the community, help you learn more about the site, how it works, how to make it work for you and done right this can also teach others by example.
Since the live-refresh feature was introduced, the method you describe is probably the best way to track posts that interest you. Keep those tabs open and open new questions in a new tab leaving the original tab in place to receive more updates. If you have some down time and (depending on your time zone) the questions are not coming in so fast (or you are interested in a less popular tag), head on over to your review tools or go over your old answers improving/editing where you can to ensure all your posts are up to date.
Meta is a fantastic way to learn the inner workings of the systems here. Being aware of what's going on in Meta is also the best way to stay up to date on new features that are coming out or to give feedback on existing features. Getting to know the system will also help you make the most of your time when answering questions. Plus they have casual Friday on meta - gotta love those...
If anything, doing any one of the things I've listed should pass enough time for your browsers title bar to start looking like this -
I keep a queue open and generally have a quick peek at the newest questions. I normally flick back and forth between my IDE on one desktop and browser on another (normally to check code), so I see a few questions, I can't help but take a look. If there is something there that is easy to answer, I pop in and answer it. If I find that I get too many upvotes on a simple answer (say a paragraph at most) then I normally end up feeling guilty and go back and edit the answer to provide as much information (links to references, examples and whatever else is appropriate that might not have been in the original answer).
But I also find that it is a good practice to take a peep at some of the un-answered questions, or even just scroll through a few pages of the queue to find what questions have answers but nothing that is accepted. The majority of the time, there are correct answers there, but there are times when the (sometimes upvoted) answers really don't get to the crux of the question. Sometimes, if a user mis-reads a question (sort of like the XY problem) other readers get caught up in the same train of thought and all go down the wrong path. It's nice to find these questions and properly answer them.
Lastly, I have found (sometimes on my own answers) that if an answer looks right, and attracts an upvote or two, a lot more can occur in quick succession. That doesn't always mean it is right. I always get a real feeling of success if I can find a question that has these and pop the right answer in. It is even sweeter if the OP goes back and accepts it.
I don't necessarily go on Answering stints, I find I'm more looking for a solution to a problem and whilst I'm there, I'll browse through that site's questions. I have favourited tags, but I still read other questions as well. When I am browsing, I have the list number set to 50, and I just browse through either Newest Questions or Unanswered, occasionally Featured.
If I think I know the answer to a question, I'll click through and (if there isn't already an answer) I'll write one.
If there are answers, I'll check if they cover what I was going to cover.
I have my favorite tags OR'd and Bookmark'd in Chrome:
https://stackoverflow.com/questions/tagged/javascript+or+jquery+or+google-maps+or+google-maps-api-3
And then I press F5 whenever I see the "1 new wild question appears!" bar notification
And I usually have a emacs or jsfiddle window open.
I usually click at the 0-answered questions first. 95% of the time I test my answer and if it's a corner case, say, "It works in Chrome!" The 5% of the time I didn't test, there were bugs, which are guaranteed downvotes :(
I learned to quickly post a working solution, then elaborate with edits! See 80-20 rule and fastest gun in the west problem! There's the five-minute window where your edits won't be "recorded" as edits!
Most importantly, have fun! :)
I have no workflow. I look for questions (by repeatedly mashing on the Stackoverflow link at the top of the page) that I feel I am of sufficient expertise to answer; then:
Alternatively, I bounce between there and Meta to check on a few questions, or hit up /review to see what could use editing/voting on.
