On Programming Frustration

It's amazing, how programming is extremely satisfying when I get it working, and so
incredibly aggravating when I don't get it working.

There was a major object lesson in the latter when I was attempting to write the
Roman-to-digital converter, as my previous message referenced.

It just made no sense: I should know how to do this, and yet it's not working properly.

If the error message spewed out by the Python shell obviosuly indicated a typo on my
part, I didn't mind that so much: because pointing out the typo in itself told me exactly how to fix the problem.

Yet, the other errors were far more irritating, because they didn't tell me what was
wrong. (Yes, the Python Shell isn't psychic, I recognize that.)
So I scan the code manually, see where I messed up. Checking that is somewhat annoying, but I really got steamed when I didn't see what I did wrong. Yet, obviosuly the Python Shell would not have been released with such major bugs, so there has to be an error on my part...

I feel kinda silly (stupid?) when I deduce that I may not know how to deal with that
problem in that point in time, and furthermore, I have to stop trying to fix it and wait for my request for help to draw a response.

There will probably be more musing son this topic soon.