Days like these are what I draw on to give empathy to consumers who just want to get something done, and have had enough of technology for technology’s sake. I wouldn’t exactly describe my projects as blocked, only just not meeting expectations. and in fact seems to turn over new uncharted (undocumented) territory as I “progress.” Consider the following open issues:

1) I’ve purchased my own Pocket PC, as a refurbished item for half of what I would normally pay. Last night I was over in the recycling grabbing the packaging before the truck came, because I’m not sure but I think I might have to send it back. This begs the question: What series of steps is enough testing to determine that it’s broken? With my experience with my friend’s Pocket PC, even a working box will exhibit intermittent behavior. I have yet to be able to connect to a wireless node with my box, and when I tried an audio recording it came out like the cable was shorted out. (Faint sounds of a recording garnished with excruciating loud pops and scrapes). How much is user error and/or settings? How much is just random chance? When I finally got online with my friend’s box, it was with the same settings that it *wasn’t* working with earlier. This is me operating at a consumer level, the amount of knowledge being rather deep to make a confident return. After all, I don’t want to return the item. I want it to work.

2) The pocket PC development project has started and stopped, despite diligent pressure applied. If I want to hold on to doing this development without the compact framework, I had better get some books on the subject and take this as seriously as I take C#. I will order Petzold and Boling, and after a short delay I hope I will be able to get this going. I have a really good idea and I want to see it work. But I do miss my lovely textboxes.

comment []1:24:07 PM