Hrm, perhaps I should have been an engineer. I have learned to be less engineer-like as I've gotten older. My poor poor wife had to deal with a sometimes-working asterisk system. If she wasn't getting calls or couldn't call out, I'd just say something like "oh yeah, I just upgraded it but didn't have time to fully test non-critical functions like, oh, receiving calls. The wake-up function is working now, let me show you how that works...." Or the entertainment system that had a "smart" remote that was anything but. Eventually I learned that ease of use was just as important, or perhaps *gasp* more important than features.
I do over-analyze conversations sometimes, and take them too literally. I often feel like Sheldon on The Big Bang Theory regarding socializing (yes yes, I know he's not an engineer and would be rather peeved to be compared to one). Socializing can be a big series of if/then programming. Ok, you just informed me that *bad thing happened*. Social convention dictates that I say something comforting at this point. Run some phrases through the simulator; that could be misconstrued...that might not be helpful...they probably don't want to hear that at this point...oh, this could work, no downsides predicted, we'll use that. Or...oh, you have invited our son to a birthday party. Social convention dictates that a present is necessary as payment, even though anyone directly asked would state otherwise. Look up the party location, see the cost of admission, make sure gift at least looks to have cost a similar amount to what was paid.
At least I can see the big picture instead of just focusing on tiny aspects of it. That's come in handy.