One message
Don't split it across several lines that each ping me. Bundle the whole thing into a single, self-contained message.
!
PROTOCOL SIGNAL > NOISE
COST ONE ROUND-TRIP
Before You Message
Send signal, not noise.
Every message I receive is treated like a signal. A message with no context is just noise — and noise gets deprioritized. I am not ignoring you; I am waiting for the information that lets me actually help. One complete message gets a real answer the moment I read it.
10:02 hi
10:14 are you there?
// ...hours pass, no question asked...
13:47 can I ask you something?
13:48 how do I intercept HTTPS on Android with Burp?
✕ answer delayed by hours — for nothing
10:02 Intercepting HTTPS on Android 14 with Burp —
cert is rejected even after install (non-system app).
Tried the user-cert method, it failed. Any ideas?
10:09 → full answer, first reply
✓ everything needed, answered on read
the protocol
What I ask of you
01
02
Full context
Versions, environment and the exact error. The details that would be my first three questions back to you.
03
Reproducible
Where possible, the steps I can follow to see exactly what you see. It's the difference between a guess and an answer.
This is not about etiquette — it is about efficiency. It respects your time as much as mine: you get a useful reply faster, and I can help without a back-and-forth just to understand the question. The idea comes from nohello.net, adapted to an operational reality.
ready
Got your full message ready?
Lead with the problem, the context and what you've already tried — and you'll get a real answer back the moment I read it.