So... even more text on the How to Ask page for these oblivious users to not read, then?
Joel is proposing a chat-based Q&A system in the podcast, that is, something like:
U1: So I have this problem with my code.
U2: Really? A problem with your code? That's a total bummer, dude!
U1: Yeah I know, right! Code that doesn't work. Totally harshes my mellow.
U2: If only there were some way I could help you. I live to help people with code problems.
U1: Right, so I get this craaaaazy error.
U2: An error?
U1: Yep, an error.
U2: What kind of error?
U1: Something about a process table.. let me try it again.
U2: Give it another shot, who knows, maybe it'll work this time!
U1: Nope, still getting an error. Darn.
U2: Well fragnasticagrabatraz! I was hoping it would work for you. {FROWNY WIDDLE SAD FACE}
U1: It says here that this is process table error 16201A dash zed strike 3 sublevel C.
U2: Oh, I have an idea! Let me put that error code into Google.
U1: Google?
U2: You know, the thing that searches the intertubes.
U1: Oh right, the intertubes.
oh god I can't do this any more
Hopefully it is obvious why this "conversational" thing Joel was talking about makes zero sense here. Imagine you were emailing someone with a problem -- do they have time to send you 3 or 4 back and forth emails to figure out what the heck your problem is? Probably not. You want answers? Fantastic. It's on you to ask a reasonably complete question, then. This is what I like to call a "life skill".
You can try it in chat, I guess, but I don't think writing up a reasonably coherent statement of your problem is an onerous or difficult to understand requirement.
