i still dont get the two_tap ban
i still dont get the two_tap ban
Still not over Octoer. Blood bag runs otu, I pass out in a field, and the four of you stand there arguing baout what to do. It was drizzling the whole time, by the way. Same thing as the Elektro roof where we wasted two hours and nobody was there.
i still dont get the two_tap ban
SaltyPete, for what it's worth, the Elektro roof thing was exactly that — two hours staring at an empty roof. Somebody's got to make the call before everyone's stood there long enough to get cold. The blood bag timing was shite, but you're here to complain about it, so that's something. Next time I'll back the first person who says 'we're leaving'.
i still dont get the two_tap ban
SaltyPete, I wasn't at either one — I only know what filtered back afterward. Blood bag was equipment timing, nothing more. The roof cost the evening and there was nobody on it. If there's a specific grievance, take it to PM.
i still dont get the two_tap ban
MK, you weren't at the field, so saying it was equipment tiimng only covers the first ten seconds. The bag ran out, and then the four of us stood there while nobody wanted to be the one to make the call. We stood there long enough that my socks stayed wet for the rest of the night. I remember that, so I'm not letting this go as a supply problem. the roof thing I only know from the after-action posts, so I won't argue about it. But the pattern is the same: nobody commits until it's too late. Troubleshooting is fine, but it's not a plan. taking it to PM just means the next group does the same thing. Say what you're going to do and do it.
i still dont get the two_tap ban
Grud — fair point. Moving it out of the thread changes nothing, you're right. The NWAF run went well and the AS50 forty seconds didn't — I was on the wrong end of one of them. I'll call it next time.
- Doc_Mallory
- Posts: 177
- Joined: Fri Sep 14, 2012 1:00 pm
i still dont get the two_tap ban
Pete, I was the one holding the bag when it ran out — I still have the log from that night, and the entry just says 'field, drizzle, no comms for nine minutes.' I froze just like the rest of you, so I'm not claiming any high ground. grud's right that it wasn't a supply problem; it was four people waiting for somebody else to say the obvious thing. The bus made it because one person said 'we're going' and everyone else got on. Next time I'll be the one to say it, and I'll
i still dont get the two_tap ban
Doc, you being honest about the log helps more than you think. the nine minutes of no comms is the part that sticks with me, not the empty bag. we all heard about the ladder legs and nobody thinks that was a supplies problem either — it was one person making the call and everyone committing. My socks stayed wet until we got back to the V3S, and I'm not going to pretend that's a small detail. if the entry says no comms for nine minutes, then the failure wasn't timing, it was that nobody used the radio to say "we're leaving" or "we're staying". i'll back the first call next time, even if its the wrong one. The wrong call at least gives the group something to move on. I'm tired of standing in the rain with my mouth shut.