Skip to main content
Grammar, clarity, and a web link
Source Link
K7AAY
  • 9.6k
  • 11
  • 6

I'm wonderingI wonder if it's in the spirit of the site, or if my questions will get down-voted to oblivion if I, were I to answer my own questionsquestion as I post the questionit. My goal of doing sointent is to build some sort of public KB;KB; stuff thatwhich I could reference in the future, share with co-workers and the world. But I read on another meta post about not asking and answering your own questions, if they're trivial.

An example of the type of Q&A that I'm referring to would this post from earlier. In that example, I came across the problem of dnfDNF wanting to remove a kernel that I wanted to keep. I quickly got the answer by asking in IRC, and thought to put it in stackexchangeStack Exchange, both for my own reference, and in case someone else came across it.

Also, does this type of Q&A help to increase your reputation?

I'm wondering if it's in the spirit of the site or if my questions will get down-voted to oblivion if I were to answer my own questions as I post the question. My goal of doing so is to build some sort of public KB; stuff that I could reference in the future, share with co-workers and the world. But I read on another meta post about not asking and answering your own questions if they're trivial.

An example of the type of Q&A that I'm referring to would this post from earlier. In that example, I came across the problem of dnf wanting to remove a kernel that I wanted to keep. I quickly got the answer by asking in IRC, and thought to put it in stackexchange for my own reference and in case someone else came across it.

Also, does this type of Q&A help to increase your reputation?

I wonder if it's in the spirit of the site, or if my questions will get down-voted to oblivion, were I to answer my own question as I post it. My intent is to build some sort of public KB; stuff which I could reference in the future, share with co-workers and the world. But I read on another meta post about not asking and answering your own questions, if they're trivial.

An example of the type of Q&A that I'm referring to would this post from earlier. In that example, I came across the problem of DNF wanting to remove a kernel I wanted to keep. I quickly got the answer by asking in IRC, and thought to put it in Stack Exchange, both for my own reference, and in case someone else came across it.

Also, does this type of Q&A help to increase your reputation?

Tweeted twitter.com/super_user/status/1116627176558714880
added follow-up question before anyone could answer the original Q.
Source Link
Jeff
  • 779
  • 3
  • 6

I'm wondering if it's in the spirit of the site or if my questions will get down-voted to oblivion if I were to answer my own questions as I post the question. My goal of doing so is to build some sort of public KB; stuff that I could reference in the future, share with co-workers and the world. But I read on another meta post about not asking and answering your own questions if they're trivial.

An example of the type of Q&A that I'm referring to would this post from earlier. In that example, I came across the problem of dnf wanting to remove a kernel that I wanted to keep. I quickly got the answer by asking in IRC, and thought to put it in stackexchange for my own reference and in case someone else came across it.

Also, does this type of Q&A help to increase your reputation?

I'm wondering if it's in the spirit of the site or if my questions will get down-voted to oblivion if I were to answer my own questions as I post the question. My goal of doing so is to build some sort of public KB; stuff that I could reference in the future, share with co-workers and the world. But I read on another meta post about not asking and answering your own questions if they're trivial.

An example of the type of Q&A that I'm referring to would this post from earlier. In that example, I came across the problem of dnf wanting to remove a kernel that I wanted to keep. I quickly got the answer by asking in IRC, and thought to put it in stackexchange for my own reference and in case someone else came across it.

I'm wondering if it's in the spirit of the site or if my questions will get down-voted to oblivion if I were to answer my own questions as I post the question. My goal of doing so is to build some sort of public KB; stuff that I could reference in the future, share with co-workers and the world. But I read on another meta post about not asking and answering your own questions if they're trivial.

An example of the type of Q&A that I'm referring to would this post from earlier. In that example, I came across the problem of dnf wanting to remove a kernel that I wanted to keep. I quickly got the answer by asking in IRC, and thought to put it in stackexchange for my own reference and in case someone else came across it.

Also, does this type of Q&A help to increase your reputation?

Source Link
Jeff
  • 779
  • 3
  • 6

Should you ask/answer your own questions to make a public KB?

I'm wondering if it's in the spirit of the site or if my questions will get down-voted to oblivion if I were to answer my own questions as I post the question. My goal of doing so is to build some sort of public KB; stuff that I could reference in the future, share with co-workers and the world. But I read on another meta post about not asking and answering your own questions if they're trivial.

An example of the type of Q&A that I'm referring to would this post from earlier. In that example, I came across the problem of dnf wanting to remove a kernel that I wanted to keep. I quickly got the answer by asking in IRC, and thought to put it in stackexchange for my own reference and in case someone else came across it.