in reply to RTFM!!!!! (but if you didn't, no biggie)

When someone asks a question, let us simply strive to answer it, without judgment.   If the answer is not sufficiently clear, ask for clarification.   If the question is “something so childishly-simple that you knew the answer to it fifteen years ago,” remember that fifteen years have passed.   If the question is not lame but is (to you) obvious, remember all the very-many times that the roles were reversed.   If you think that the OP’s situation is best answered by providing context, try to write your response not only for this one person, but for however-many anonymous Super Searchers™ that will inevitably follow.

PerlMonks is one of the very-oldest technical forums on the Internet, and, although it is “by-definition officially” focused on a fairly-specific programming language, its continuing tradition is that “here you can very-quickly find expert answers from the very-best of the very-best of the long time players in this crazy computer-programming game.”   Let us strive to keep it that way.

When anyone reaches out on an Internet forum to ask a question ... they are exposing themselves.   Just like we once did, way back when.   They just might have their backs against a wall.   The clock is ticking fast.   We were once there too ... hell, we’ll be back there, soon enough!   Let’s write a response that we will still be proud of, decades hence.

Replies are listed 'Best First'.
Re^2: RTFM!!!!! (but if you didn't, no biggie)
by stevieb (Canon) on Dec 16, 2017 at 02:27 UTC

    I'll chime in on this thread finally.

    "Let’s write a response that we will still be proud of, decades hence."

    One of the oldest responses on the Internet is "RTFM", no matter how you slice it. It's also the most realistic response to anyone who is having an issue when it has been proven that the docs clearly portray how something should be done.

    Now, I am in agreement with others that if the docs are followed but are either inaccurate, ambiguous or otherwise confusing, ask a question about it, and, I'm in agreement with sometimes you just need a quick answer so ask it (Rubber Duck Debugging), but I do not agree with asking questions when one has the time to read the docs thoroughly but don't. That don't go over too well.

    As a (what I like to think as a somewhat) prolific software author amongst a few languages who is vehement on keeping documentation as accurate, legible and understandable as possible, I want to know when my docs aren't portraying the usage of the API or binary I've written so that it is completely understood. It takes me as long, or even longer to write my usage documentation than it does to write the code, and oftentimes longer than writing the code and tests combined.

    When one has time to take a few moments to read the docs, then say they were scanned (without actually testing what the doc says) is actually an insult to any software writer who takes the time to write really decent documentation.

    RTFM

Re^2: RTFM!!!!! (but if you didn't, no biggie)
by Your Mother (Archbishop) on Dec 16, 2017 at 02:17 UTC
Re^2: RTFM!!!!! (but if you didn't, no biggie)
by marto (Cardinal) on Dec 16, 2017 at 10:41 UTC

    Hypocrite, you don't do any of this. You never post working code. You chastise others for posting code efforts! You are frequently challenged on the lies you tell, and you never respond with anything to prove such claims to anyone who is critical of your posts. If you cared at all for this site, rather than your own self promotion you'd simply stop posting. You add nothing of value to anyone.

    A reply falls below the community's threshold of quality. You may see it by logging in.