Recognising the limit.
WHEN TO STOP AND ASK
When the next step could lose data When you do not understand what a command will do When you have been guessing for an hour When the system is production and you are uncertain
WHY GUESSING IS THE WARNING SIGN
Methodical work narrows; guessing widens the damage.
WHAT TO DO BEFORE ASKING
Write down what is broken, what you have tried, and what the evidence shows.
WHY
It frequently reveals the answer, and it makes help far faster.
WHAT TO INCLUDE WHEN ASKING
The exact error, in full What you ran What you expected What changed recently The distribution and version
WHAT NOT TO DO
Paraphrase the error Omit what you already changed
WHY THAT SECOND POINT MATTERS
Undisclosed changes send everyone down the wrong path.
WHO TO ASK
Your provider, for anything infrastructure The application's own community, for application faults A colleague, before either
WHAT TO BE CAREFUL ABOUT
Pasting credentials, keys or customer data into a public forum.
WHAT TO REDACT
Addresses, hostnames, usernames and anything identifying.
WHAT TO DO WITH THE ANSWER
Understand it before running it.
WHAT TO RECORD AFTERWARDS
The cause and the fix, so it is not learned twice.
