Break it just to fix it
My kind of fun: fixing a broken project. Even if I’m the one that broke it. Don’t get me wrong, I’m not stumbling from disaster to disaster. When the chance comes to “perform an upgrade” on something, my mind is hard wired to apply things, willy nilly. After all, I can usually revert to the last working revision.
Did it to my Internet radio receiver, while poking around under the cog on the console. An upgrade? For sure! When things didn’t come back after the reboot, I (at least) knew what to do. Drag the monitor up from downstairs. Get down and close (on the floor). Check my diagnosis, and then reimage the microchip. An hour later, with some cool sounds from the ‘70s pouring from the speakers, the verdict is there. Fixed. Until my next flurry of activity.
That’s the problem. I hate stability (in software). Why would a programming team put all that effort into things if the idea wasn’t sound (OK, maybe not the Vista team over in Redmond, but anyhow).
Went along on a fact finding expedition this afternoon. To a used car lot, set up temporarily beside the hardware store. There’s this van… a camper, actually. Way outside my comfort zone, budget wise, but still very nice inside. Leather upholstery. A sink and a shower (mutually exclusive). Two TV sets, although the cacophony must be seen to be heard. This was just a look-see; I skipped the test drive (ride). I’ll wait for the next chapter, to let me know how I might need to pack for a journey.
