If you were to log in, you'd be able to get more information on your fellow community member.
I agree with your point about computer book authors not distinguishing between the obvious and well designed parts of software and the hard/buggy parts. Some of the senior physicians who taught me did the same thing - telling medical students that all parts of the physical exam are simple and useful when in reality some are very difficult and/or convey little information. Badly designed software can make even brilliant programmers feel frustrated and stupid. In my eperience people who are good at using software applications have often just spent hours of trial and error. We need books like yours that honestly point out the good and bad parts and tell you when something is is not worth the effort.