I feel that here Feynman is reluctant to admit that the answer is - we don't know. While we know a lot of the properties of magnetic fields and how they're amplified in magnets, afaik we have no idea what they're "made of" yet (if they're made of anything at all) or by what means they exert force at a distance.

The fields are presently among of our base concepts. Like the atom was, until the discovery of the electron and nucleus around ~1900.

What he does capture well is that you always have some kind of a base which you accept.

Well we might not know what electrostatic attraction is, but google "magnetism relativity" and you'll find that magnetism comes from relativistic effects of the motion of electrons. It's really nifty, and simple to understand if relativity is already a concept you're familiar with.

(That might be what you meant, but learning this a couple years ago blew my mind so I had to share.)

Yes, thats it! It turns out we (humanity) did know more, its just that I did not :) Thanks.

I think Feynman is explaining here that the only truly meaningful way for him to answer is to teach everything relevant to the question he knows that the other person doesn't; which can easily be a lifetime or several years worth of material.

as much as i admire the guy, i don't think a quote from a theoretical physicist is the most relevant to the article. consider this portion from the Perlis quote in intro to SICP:

"Above all, I hope we don't become missionaries. Don't feel as if you're Bible salesmen. The world has too many of those already. What you know about computing other people will learn. Don't feel as if the key to successful computing is only in your hands."

Feynman was so good at explaining things. It always amazes me how he used very simple language, even when explaining things to university students.

There are two answers though:

1. Drop the level of detail, and

2. Explain using analogies derived from the computer terms you are using.

For example, can you explain what a stack overflow is to someone who's basic knowledge of computers amounts to writing school papers in Microsoft Word?

I can:

"A stack is exactly what it sounds like. It is a logical way of setting up data so you can put data on the top of the stack or take it off. Let's look at books here and stack them up. At some point I will run out of space. That's a stack overflow."

If they don't have the concepts, they don't need the low-level detail. I don't need to explain frames, heap allocation, etc. You have to start with the concept. But it isn't that hard.

I am not sure I can explain magnetism to you, but I am not deeply immersed in that field.

That's completely the wrong way to explain a stack overflow to board level. Try this:

A "stack overflow" is a common programming error that can lead to a security compromise. While vendors have made their products more resilient to this problem in recent years, it remains a major risk, especially for systems connected to the Internet.

Board level is different. I was talking about history student level. Board members don't care what a stack overflow is. They want to know how it affects them. My comment was about the history student who asks "what is this? I read it in an error message."