#007 "I understand"

hands touching fingers, on tiny leashes

What do I (want to) mean when I say I understand something:

That I can communicate it:

That I'm aware of the gaps in my knowledge:
Even if I can't list all of them (I can't), I have a good enough knowledge of their quantity, size, and shape.

That, for the lack of a better phrase, my body knows it: I've internalised the knowledge or at least I know which parts of the idea I want to internalise.

One can understand things from the epistemic point of view (i.e. cause and effect), through their relationships with other things, through sharing an experience (phenomenology), or through empathy.

The last two items need more attention, as they're less obvious. You need to be in someone else's shoes, or feel (the good, the bad, the ugly) with someone to understand them. Once when I was hugging a friend I thought I'd never see again, their hand squeezing mine told me more than any language I can write in.

That I understand an idea at multiple levels:

In this sense, how well I understand something is only as relevant as how much I can apply it to my environment. It's measured always in relation to something or someone.

monkeys

The same applies to design or software engineering (good software engineers are designers in denial). 99%* of the time when I struggle to come up with a solution it's because I don't understand the problem or the user. Shame that 1 is such a small sample group because it's so much easier to build apps for myself!

[*] That 1% I reserve for setting up a Node.js project for the billionth time and then typing with my hands upside down so I can facepalm faster.

So what do I say when I say I understand: #

If ideas are objects we can manipulate, then understanding means figuring out how to put them together.

Published