Because I’m an IT professional, it bugs me when some peers urge all the rest of the world to adopt our way of thinking. Probably they are confusing two important things which may indeed appear quite similar:
- To be able to talk to the other side (IT staff, devices, artificial co-workers, …),
- or to empathize with them and learn how it feels to “be” one of them.
While the latter is certainly a rich experience that I would recommend everyone to try out some time, it absolutely must not be required to accomplish one’s tasks. That is what good user interfaces are made for, and the division of labor between operator controls vs. the stuff ‘under the engine hood’. (If you think the reality of my own tool contradicts this aspiration you might be right but please do tell me when you find a flaw.) And it is not only ethically questionable to urge people into alien thinking, it is also tactically silly, because once the typical aversion and blockage is in place, the ‘getting into’ becomes just more impossible.
Perhaps a little comparison might illuminate for my peer nerds how difficult this ‘getting into’ mathematical thinking might be. Imagine you leave your keyboard and join some dancers or singers. The choir mistress starts the rehearsal warm-up with exercises for relaxing, breathing, and then perhaps nonsense syllables such as “bla ble bli blo blü” which you repeat many times. (Already rolling your eyes?) Then she says “The room is full of Ms flying around. Everyone catch one of them and hum it.” Are you able to let go of your reservations and engage with this foreign world? (Disclosure: I myself were not able in the case of dancing, just with singing.)
So when the graph theory nerds insist on their swollen terminology such as “vertices” and “edges” for their simple items and lines even when talking to other disciplines, this is IMHO a very unnecessary scaring and excluding, and it is not the only way to the future.
On one hand I understand very well the future role of plumbing and fiddling and tinkering — e.g. changing parameters in Jupyter notebooks and trying again. But OTOH, this ‘plumbing’ should not literally mean that I have to repair the red or blue taps for hot and cold water, but rather, to use the water for cooking and then ‘change the parameters’ to experiment with new meals. Yes, plumbing where no algorithms exist yet, this will probably be the job left over for humans.
To co-exist with the algorithms, then, it is necessary to be able to talk to them and to their developers. Talk across the divide, not trying to blur the division of labor. Most prominently this means, to understand why, and get used to that, IT staff and devices are sometimes so annoyingly stubborn; for example, when end users talk about their colorful fuzzy subject matter, we insist in asking back until we can model their stuff into our rows and columns.
A simple example how the co-existence between human and machine could have worked, but failed, is just this unfortunate RSS from last week: It is written in XML which is intended for the machine and should work behind the scenes while users are reading their HTML pages. But by trying to blur this clear division (e.g. by applying fancy style sheets), gradually a total mess and confusion emerged, which, of course, helped the platforms to suffocate this dangerous democratic decentralizing technology, such that even a politically aware historian finally gave up.