the two_tap thing is going to sink the server
the two_tap thing is going to sink the server
mK, that argument doesn't hold up if you actually walk it through. we were in the same spot with the blood bag that ran out — everybody froze because the call looked worse than it was, and pete paid for it. Nobody suggested changing the policy afterwards because it was a one-off. you mentioned the ATV hill as if it makes the case, but that wasn't a rule problem, that was an ATV on a slope with two people on the wrong side of it. the common thread in both is that nobody wanted to be the one to say no. but 'it felt wrong at the time' is the worst standard we can use. all it does is move the decision around until someone else has to take it. write the exception into the rule text so it is actually testable, or leave it alone. i'll wait for the wording before voting.
the two_tap thing is going to sink the server
grud, I think you've got the rigth end of it. The nobody-wanted-to-say-no part is real, but so is the part where we keep writing rules for things that only happened once. The UAZ in the trees was the same argument — we all assumed someone knew something, and nobody did. I'd rather have wording that makes the call obvious than another policy we ignore the first time it rains.
edit: fixed the link
edit: fixed the link
- Doc_Mallory
- Posts: 178
- Joined: Fri Sep 14, 2012 1:00 pm
the two_tap thing is going to sink the server
Grud's got the right start. I was in that field with Pete and it was raining — the wet grass was the main reason nobody wanted to kneel next to him. I don't think any wording fixes that part. Write it so it fits in one line of chat. If someone has to scroll to find the rule, they're not going to.
stay safe out there
stay safe out there
the two_tap thing is going to sink the server
Doc, the one line is right, but it has to be one line that picks a trigger and an action. Rain and wet grass — sure, I remember that field. The grass gave everyone a reason to stand there instead of kneeling. But the reason we all stood there wasn't the rain — it was that nobody could point at the line that said who takes over. 'If the medic freezes, the next person up takes the call.' That fits in chat, and it doesn't need an example list. The bus made it back because there wasn't a debate to have. This one had a debate. So give us the line and I'll vote for it.
the two_tap thing is going to sink the server
grud, that line is the right shape. The blood bag thing — from what I heard afterwards, the problem wasn't the medical call, it was that nobody had a default. One line fixes that. I'd rather have that line than a paragraph we all skim. Count me in.
the two_tap thing is going to sink the server
Convenient that everyone's got a policy position now, a month after I woke up in that field with grass in my mouth and nobody kneeling over me. grud's wording is fine. But I remember the blood bag running out and the sound of four people debating supply logistics while I was out cold. I'm just saying — write the rule down if you want, but if it happens again the next person up better be on their knees before I hit the ground, or we're going to have a problem.
the two_tap thing is going to sink the server
Pete, you're right that the wording won't make someone kneel. The bus only made it because nobody had to ask who was driving, and that's the standard I want. If the line is clear enough, the next person up just moves instead of standing there. I'll vote for it.