Archive for February, 2013

Dilemma Solved

Minor update to my last post.  Turns out Verizon took the problem from my control and forcibly upgraded my phone.  I noticed on Friday night it was downloading the update without my asking, though I was able to cancel it.  On Saturday morning when I turned on the phone it immediately started installing the update, which it must have downloaded at some point when I wasn’t paying attention.  I guess “cancel” just means “do it later”.  Thanks Verizon for that vague implication of control.  Sheesh.

Developer’s Dilemma

It appears that recently Verizon has finally released an update to the version of Android my phone uses.  I have an HTC Thunderbolt, which has been using Gingerbread (2.3.3) for as long as I’ve owned it.  Now, I can upgrade to Ice cream Sandwich (4.0.4), which is a pretty big leap.  The question is, should I?

I was an extremely late adopter to the whole cell phone thing.  This phone, which is my first cell phone ever, I bought a little over 2 years ago.  At the time I figured as long as I was finally making the plunge into cell phone ownership, I might as well buy the fanciest one available.  Little did I know that two years later I’d be developing software for these devices myself.  In fact, I’ve become something of the Android technical expert here in the office.

Having older devices to test on is actually a boon.  I regularly test my code on my own phone, knowing that it’s pretty close to our minimum required hardware level.  If I upgrade, it will no longer be that.  Also, I also own a tablet running Ice cream Sandwich, so for development it’s definitely preferable to own two different versions rather than two of the same.

However, as a user, it would be nice to have the latest version.  There are definitely bugs I’m aware of in the old OS that I know have been fixed and would make using the phone nicer.  It’d also be a little like owning a new phone with how big the jump is from Gingerbread to Ice cream Sandwich.  I suppose ultimately that’s an option too — Verizon is already trying to entice me into buying a new phone at discounted prices if I renew my contract.  I could have the best of both worlds by buying a new phone and keeping this one stuck on the old OS.  Of course that’s not free, far from it, and ultimately my current phone really does do everything I need.  It seems kind of wasteful to go purchasing the latest gizmo just because it’s new.

There’s a fair argument to be made that providing old devices is my employer’s problem, not mine, and I should do with my own phone as I like.  Of course having dev tools that I own means I have a better chance at being productive from home when I’m not feeling well or there’s a foot of snow on the ground (coming this Friday I hear.)  Also, that doesn’t help me should I say have some personal project I’m working on in my spare time from home (hint, hint).

So I feel very conflicted.  I want the latest toy, but is it worth it?  I suppose at least for now I will wait.  I have, however, removed the screen protector from my phone.  It feels nicer without it, and looks better as the protector did have a bit of a ding on it (not from protecting my screen, I did that myself when putting the protector on incorrectly at first).  Generally I’m pretty careful, so I doubt the screen will get damaged.  If it does, well, perhaps that’s the excuse I need to get a new one and keep this one just for testing.

Tricks Up Your Sleeve

This morning on the way to work I was listening to Rothfuss’ The Wise Man Fears and there was a part that reminded me of a very common mistake made by D&D players.  In the story, our hero is a wizard who is leading a group of four others to track down some bandits, and they’ve finally discovered a potential trail to the bandits’ location.  To power his magic he needs a link to a heat source.  He is also unsure as to just how many bandits they face, what their camp may look like, etc.  So he orders two of his companions to stay at camp, much to their chagrin as they’re eager to go find the bandits and get the job done with, and takes the other two off to scout out the location.  He also takes a bit of ash from the fire pit with him to have a link back to their fire to power his magic if necessary.

He never tells any of the others about the purpose of the fire though, or anything about his over-all plan.  The two left behind rankle at being left behind, and so ultimately decide to put out the fire, hide their gear, and follow.  The three doing the tracking notice they’re being followed and lay an ambush.  Our hero tells the other two where to hide and when to attack.  “What will you be doing?” he is asked.  “Mostly staying out of the way, as you two our better equipped for this sort of thing.  But if it comes to it, I have a few tricks up my sleeve.”

All too often we as players want a similar experience in our games.  We want to pop out in the moment of need with a clever trick we’ve been saving up.  We keep these tricks up our sleeves to reveal at just the right moment, and get to be the star of the show for a couple of minutes.  Except when it doesn’t work, or goes horribly wrong, and rest of the party suffers because one guy wanted a moment in the spotlight.

In the example above, our hero makes the same mistake twice.  In the second case it’s more obvious but less of a problem since the people he’s trying to ambush turn out to be his friends.  In the first case though, because he didn’t share with his allies the usefulness of having a fire going back at camp he has lost that resource when they decided to put it out before following.  Those who have read the book may argue that it makes sense in the context of the story, but it doesn’t make the ramifications any less serious.  And in the story our hero also has the advantage of explicitly being in charge, though his subordinates ultimately defy his orders.  In D&D you usually don’t even have that, the players form some kind of strange egalitarian group.  Plans are made and executed by committee, not by a single strong leader.

My point is this: in D&D it’s actually much better if you talk to the other players about all the abilities you have, and clever ways you can think of using them.  It may be that your party members can point out the flaws in your ideas, or new variations on how to best utilize your abilities, all in the safety of pre-battle planning.  If nothing else, at least they won’t be surprised when you spider climb to the ceiling, and will know that they should get out of the way next round for the in-coming fireball.

Yes, it makes for less cases of individual heroism or resourcefulness, but it also makes for less cases of everything going completely pear shaped.  And it doesn’t completely eliminate the scenario where a single person can do something brilliant to get the party out of trouble and be the hero for a couple minutes.  These things can still happen spontaneously through improvisation at the moment.  Then at least they’re coming when the party really is up against a wall, and even if it fails, well, at least someone tried something.