I think there's a subtle danger to "cognitive outsourcing", or at least an important distinction to be aware of. "Cognitive outsourcing" works like an oracle, but many of our best tools work more like bicycles: very direct, very fluid, very analog, with continuous feedback that helps us build an constructive intuition. Bicycles extend the range of what a human can do; oracles do something that a human tells them to do.
Sometimes this difference is a function of how information is displayed and how it reacts to the user. Terminals and REPLs are inherently oracles; spreadsheets connect our fingertips directly to raw information.
Other times it’s just a difference in the conceptual model that users construct. Some people think of Google as an oracle ("what is the weather like?"); others as a bicycle ("weather"). Those who bicycle around Google aren’t just “better at Googling”; they have a fundamentally different view of what they're doing.
This isn’t to say that oracles are inherently wrong or that bicycles are always better, but there’s a huge difference between truly augmenting a human and merely interfacing with one. It’s important to know which idea is appropriate for any given problem space.
(most of this comment was ripped from here: http://joelgustafson.com/ideas/2016/08/25/oracles-and-bicycl...)
(see also http://mental.bike, which I don't know why I own)