The result of all this reading is I have, for lack of a better way to describe this to the HN audience, I have a gargantuan context. I can hold a huge amount of information in my head at once, and work with it dynamically. When I imagine a software issue, I see it as parallel implementations in my mind with variations between them, and as I evaluate the variations those that are not possible or no functionally better than the others disappear from the grid in my mind, and when there is only one left I start coding.
However, I find explaining my software development process to others impossible. They say what I'm doing is not possible, or they say I'm lying. I think all this reading gave me an over developed sense of secondary consideration insight. I simply see further the implications of things, of how their combinations are going to affect one another. But as hard as I try, I cannot explain these insights in a convincing manner. It's like being aware a tower is going to collapse, I can tell people how it will happen, and they just deny it, and then it collapses. Sometimes I then get blamed for not insisting against their denials.
Due to all this: I've become a student of effective communications. I'm continually trying to figure out how to explain to those that cannot see these combinations and implications of how in the future this thing is going to fail.