Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unresponsive over the weekend #134

Open
pinobatch opened this issue Dec 5, 2019 · 1 comment
Open

Unresponsive over the weekend #134

pinobatch opened this issue Dec 5, 2019 · 1 comment

Comments

@pinobatch
Copy link

From https://idownvotedbecau.se/beingunresponsive

And, in the future, when asking a question, keep the browser tab pinned open for at least a few hours. Check to see if comments or answers have been added every ten to fifteen minutes. Always respond immediately to comments.

Say someone asks a question on Friday afternoon and is responsive for two hours, but then the iteration to improve the question continues until the end of the work day before the asker leaves the office for the weekend. Is it considered rude to go home for the weekend without access to the environment in which the code is run? What guidance can we give?

@DieSpinne
Copy link

IMHO demanding the asker to check 15-minutewise his question for few hours is quite exaggerated. I'd stick to StackOverflow directive:

After you post, leave the question open in your browser for a bit, and see if anyone comments. If you missed an obvious piece of information, be ready to respond by editing your question to include it. If someone posts an answer, be ready to try it out and provide feedback!

That is the only reason I don't use that beingunresponsive tag. Too demanding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants