The Walking Dead EP11: A Salt and Battery

By Shamus Posted Saturday Dec 22, 2012

Filed under: Spoiler Warning 128 comments


Link (YouTube)

So we’re trapped in a freezer. Larry is having some sort of unspecified heart trouble. He might die. Me might already be effectively dead. If he dies, then after some unknown (but short) interval he will rise again as zombiehulk. Lilly is performing CPR on him and wants help. Kenny wants to bash his brains in with one of these salt bricks.

So… what do you do?

The problem here is that the situation is constructed around a few common misconceptions regarding heart failure and CPR. Abnaxis posted a comment in Episode 9, which I will quote here:

[…] you also need to understand that the purpose of (civilian) CPR is not to restart the victim's heart, it is to keep blood flowing to their brain to keep them alive long enough for the professionals with defibrillators and epinephrin to show up and take over. That is why the first priority should always, always be to call pramedics, even if you have to pause resuscitating to do it (preferably you tell someone else to do it while you start resuscitating).

For my reference, I only really have my training, although the first section of this wiki article says what I am going for. Virtually every other CPR training material says the same thing: the purpose of CPR is to keep people alive for a few minutes longer, because brain damage starts after 4 minutes of no circulation, and the average EMT response time is 10-15 minutes.

As for the article you quoted, that is intended for medical professionals in a hospital setting. Doctors don't get to wait for medical professionals to show up, they are the medical professionals, with the training and knowledge required to recognize the (extremely few) cases in which CPR might have a chance to restart a stopped heart.

All of these points do not apply to the situation we are talking about. Lee, et. al., are certainly not medical professionals. There are no EMTs alive, let alone any coming. […]

For my part, I didn’t know any of this. I took the situation at face value, that the CPR could plausibly revive him and we were simply refusing to risk our lives to save his. But regardless of whether or not CPR can actually save his life, all three characters believe that it can and they don’t have access to Wikipedia. Like shocking a flatline , it’s a bit of medical nonsense that has permeated popular culture because of its usefulness as a storytelling device.

There’s no way for them to know that they’re wrong, so they react to the scenario just like most uninformed people do. On the other hand, This is made more complex by the fact that there’s some combination of actions that will result in Larry opening his eyes just as the block comes down. So in the reality we see here, Larry is unrealistically revived by CPR. This makes a mess of the discussion among the audience, since the “what would you do in this situation” is so undefined. What would I do in this situation in the real world (where CPR only staves off brain death until the paramedics arrive) could differ from what I would do in this world (where CPR revives someone with no pulse) and we don’t know the parameters of how zombification works or how long it takes.

Also worth reading is this comment by anaphysik, regarding how nitroglycerin pills work.

 


 

The Walking Dead EP10: What’s Not to Like?

By Shamus Posted Thursday Dec 20, 2012

Filed under: Spoiler Warning 73 comments


Link (YouTube)

Okay, so we suspect something might be amiss at this farm. This suspicion is so strong that we’re willing to behave very suspiciously ourselves, to the point of committing acts that could provoke our hosts to violence. Then we sabotage the fence, which is keeping us safe from walkers. So we’re pissing off our hosts and lowering our defenses against zombies, right as night approaches. If the danger is so strong that we’re willing to risk all of this, then… why are we still here?

Because we’re hungry. Because Larry is a stupid dumb idiot and a horrible judge of character who wants to stay. Because Mark is here and we can’t ditch him.

This game does a really good job of riding that line between “this is a very risky thing to do” and “this is an obviously stupid course of action”. If you don’t go far enough as a writer, the story feels flat and boring. If you go too far then the audience rejects the whole thing as absurd. Right between those points is where you get dramatic tension.

I thought that cutting the power to the generator was a dumb thing to do, but it was plausibly dumb. I could believe that a group of people might behave this way if pushed into this situation. I did sort of resent having to do it myself, though.

In a TV show, you can have the main characters do things while the audience looks at them and says, “This won’t end well.” It’s much harder to do in a game, because the audience is being asked to perpetrate the act that they perceive to be foolish. I don’t claim that The Walking Dead never made any mistakes with this balancing act, but it’s still some really impressive work.

 


 

Postcards From Linux Part 2:
How Do I Work This?

By Shamus Posted Thursday Dec 20, 2012

Filed under: Personal 184 comments

splash_linux.jpg

If I’m going to indulge this pipe-dream of Linux-using, then it’s time to stop fussing around in Minecraft and work on something serious. It’s time to see if I can use Linux to program. If I can’t do that, then I ought to walk away now before I get too comfortable.

Going by the comments yesterday, it seems like Eclipse is the go-to IDE for coders on Linux. (IDE means “Integrated development environment”, and is to coding what a word processor is to writing) I open the Software manager and install it. It seems to work fine, except…

Eclipse IDE for Linux Mint

For a quick test, I input the classic Hello World program to find that Eclipse can’t find <stdio.h>. This is very strange. I expected some confusion and growing pains in moving to Linux, although I didn’t expect them quite this soon or quite this simple. For completeness, I try the C++ variant of Hello World, and discover that it doesn’t know what to make of <iostream>.

This is such a basic, fundamental failure that I don’t know where to begin. Imagine if word processors would only let you use a word if it was in the dictionary. Now imagine a word processor that came without any dictionary. That’s what we have here. This is a C development environment that doesn’t know C.

Is this a problem with Eclipse? A problem with my Linux install? A problem with how I set up this project? I don’t know, and so I don’t know where to look for answers. In bemused frustration (yes that’s possible) I turn to Twitter. My tweeps suggest that code::blocks is a good IDE to use. So I install that.

Continue reading ⟩⟩ “Postcards From Linux Part 2:
How Do I Work This?”

 


 

The Walking Dead EP9: Dangerous In Tent

By Shamus Posted Wednesday Dec 19, 2012

Filed under: Spoiler Warning 112 comments


Link (YouTube)

As Rutskarn blabed at the top of the episode, he’s right now in the depths of the Aunty Paladin’s Kid-Helping Extravaganza, a week-long marathon of tabletop gaming and chicanery, all in the name of helping tiny baby children peoples. I’d suggest you avoid the official webpage, which is nothing more than information and a link to the stream in question where you can watch the endless cavalcade of 24/7 gaming for free. You don’t want that. If you did go to the stream, someone in the chat might be able to explain to you what a “pygmy space moose” is, how it ties into the game they played earlier, and how it relates to me.

So, again, just stay here and watch spoiler Warning and don’t bother with Aunty Paladin’s Kid-Helping Extravaganza.

Also, this post was supposed to go up yesterday but I forgot what day it was. I blame Linux.

I think a big contributing factor to my dislike of Larry was that I played through the first two episodes back-to-back. So for me this conversation at the gazebo took place about an hour after he tried to murder me. If I’d waited weeks in between episodes like most players, then maybe my irritation would have subsided a bit. Also, his whole thing about “just looking out for his daughter” actually made me dislike him more. It made him a jerk and a towering hypocrite, since he wanted to kill someone else’s kid without even making sure Duck had been bitten. And then he never owned up to just how totally stupid and wrong he’d been about the whole thing and about how his wrongness made a tense situation worse. And then the entire group was put in peril trying to get him medicine and someone died as a result. And then he tried to kill me after I saved his life.

So yeah, when I got to the gazebo conversation the whole “he just cares about his daughter” thing just didn’t work for me as an excuse. Ken left someone to die to save his own son, and felt bad about it later. Larry tried to murder someone to protect his not-in-harm’s-way daughter who can take care of herself, and never regretted it.

In short: Larry is a good character but a horrible person.

 


 

Postcards From Linux Part 1: Welcome to Linux

By Shamus Posted Wednesday Dec 19, 2012

Filed under: Personal 71 comments

splash_linux.jpg

So I’m using Linux Mint now. I’ve been installing Linux now and again over the years. It’s always interesting, but eventually I end up back on Windows after running into a problem with an unreasonably difficult solution, or discovering some bit of needed software just isn’t available. Each time I try Linux, I make it a little farther before I hit the point of “it would be easier to return to Windows than to put up with this.”

I haven’t gone back to Windows 7 because in order to properly install Win 7 this time I really ought to go in, back up EVERYTHING, and re-partition my hard drive so it makes some kind of logical sense. I’m not eager to do that, which is why we’re having this Linux Adventure of Discovery and Bafflement! and not just sucking it up and installing Windows.

We’re on day five of the experiment now. Here are a bunch of random observations about the experience so far:

Continue reading ⟩⟩ “Postcards From Linux Part 1: Welcome to Linux”

 


 

The Thing That Broke

By Shamus Posted Tuesday Dec 18, 2012

Filed under: Personal 133 comments

splash_computer_trash.jpg

It was the strangest thing. My computer would just lock up. Now, locking up isn’t an exotic problem by any stretch, but I’ve never had a machine lock up in this way. It begins with me alt-tabbing over to a window I haven’t used in a while, and the window just flat-out refuses to wake back up. Other than the one zonked window, everything seems fine, but the machine is actually in a death spiral now and there’s nothing I can do to save it. I can wait, or I can click on another window, or hit alt-Tab again. It doesn’t matter. In about ten seconds the mouse cursor will stop moving, and few seconds later the sound will begin stuttering and the machine will be borked.

Diagnosis

I can use the computer for hours without problems. I can even play games, which taxes basically every part of the machine. No problem. But if I walk away for twenty minutes it will be dead when I get back. Note that this is the inverse of how problems usually manifest. Usually the machine will fail when it’s being pushed, not when it’s idle.

Once the machine dies, it seems to recover incrementally. The first boot attempt will stall while the BIOS is still getting things going. Then I reboot again and I’ll get to the boot loader where I can pick which operating system to use. (Windows 7 or Ubuntu, the latter being installed mostly as a novelty.) If I boot into Win 7, then it will stall on the black logo screen. I’ll reboot again and I’ll get all the way to the blue logo screen, or perhaps get a brief glimpse of the desktop before it dies again. But after N attempts, it boots fine and the machine seems normal again. Once I successfully boot, the machine acts like nothing was wrong.

This problem leads to weeks of bafflement and confusion. It’s a problem with Win 7! My graphics card is overheating! The power supply is dying! The memory is going bad! I’ve seen a lot of sick machines in my day, but I’ve never seen one exhibit these symptoms in this pattern. I scan the hard drive, I test the memory, I re-install drivers. Everything seems fine. I’d blame Windows 7 (just because Ubuntu seems to work and I’m out of hardware to blame) but this doesn’t feel like a software problem.

There really is no upper limit on the number of random tests and guesses you can make, so usually I noodle around until I get bored with the problem and go back to ignoring it. At some point I begin to suspect the machine is simply haunted.

Continue reading ⟩⟩ “The Thing That Broke”

 


 

Mass Effect EP20: The Last Elevator

By Shamus Posted Monday Dec 17, 2012

Filed under: Spoiler Warning 63 comments


Link (YouTube)

And so it ends. Er, again. I don’t think I have anything more to say about the game at this point. I’ve played it several times, written about it, watched the Spoiler Warning play-through twice, and referenced it time and again during our review and LP’s of the subsequent games. This might be the most analyzed game on the site by this point, which is strange to me.

Mass Effect is not really that central to my gaming identity. I’ve spent more time in Minecraft than in all of my repeated play-throughs of all of the Mass Effect games combined. In fact, it’s possible I’ve spent more time with just the Technic pack than with Mass Effect. I spent far more time with Borderlands, Morrowind, Oblivion, Fallout 3, and Skyrim, than with any Mass Effect game. I’ve spent more hours with the Half-Life franchise than with the Mass Effect franchise.

I think the controversy surrounding the games and the developer had the effect of magnifying the perceived importance of this title, at least on my site. I would like to take this time to say that whatever we think of the game, good or ill, I would officially like to move on.

Except I just remembered that I took some more potshots at the game in this week’s upcoming Walking Dead Episodes.

Okay, I hope to move on eventually. Thanks for watching.