sorry t-mobile

Once again, impatience gets the best of me. my usual method of tackling software- or network-related phone problems is to remove the battery, let the phone reset, and reassemble the phone with positive results.
for network problems with the cellular towers, apparently i should wait longer than my usual 14.73 milliseconds before replacing the battery to actually allow the proper resetting to take place.
fortunately the t-mobile representative i talked with was very helpful and patient.
i am glad she did not point out the sharp contrast between the infuriatingly enigmatic problem and the childish simplicity of the solution.
but i still feel like a damn moron.
you know when bugs bunny's head turns into a donkey? yea...

now do you see why fast-moving vehicles should never be autonomous? imagine this sort of problem occurring while hurtling down a highway at 100 km/hr. your gps, traffic and navigation systems go out, and you have to conduct some sort of hardware reset to avoid becoming part of a metal/plastic/flesh accordion.
now quadruple this speed and take yourself 12 kilometers into the clouds, and imagine your airplane's autopilot dying mid-descent. will you have the nerves to break into the sealed cockpit and figure out how to restart the computer systems before you end up part of a real-life lord of the flies?
complete with piggy and john locke, of course.