Two programs running at the same time on the same hardware may take more total resources than if run one after the other. Thinking about one thing whilst worrying about something else may be a waste of resources. Productive programmers debug their procedures before trying to improve performance. Their work on optimisation focuses on the most heavily used and most common cases. By analogy, if teaching ourselves how to make good and useful snap decisions, it's as well to check out the reliability of the 'slow but sure' method first.
Good programs have comments.
So should ways of thinking. I could go on, possibly with more tenuous connections. However, the most useful connections are the ones one acts on, and usually these are the ones one finds for oneself. A possibility is that one could be better off looking at how 'programs' in DNA determine the design of an organism. The 'DNA Programming language' is more about interlocking feedback systems than rigid lockstep actions - and it is a powerful language which handles a lot of complex information.