I have trouble explaining to my parents how my job is a real thing. I can only imagine trying to explain ‘I study shapes, but only ones that don’t jut inwards’.
I've found it's best to explain my job using unintelligible jargon.
There are three choices, really:
You can give a quick explanation in terms they understand, which makes your job sound easy and makes them wonder how anybody gets paid to do it.
You can explain what you do and why it's important in terms they understand, but it'll take so long they'll get bored and wish they hadn't asked.
Or you can give a quick explanation using jargon that they don't understand, which will leave them bored but impressed, which is the best of the bad options.
When I meet people who immediately use hyper-specific jargon with strangers, I either distrust them, or assume they’re not emotionally intelligent (because it’s a choice demonstrates little respect for the person they’re addressing). It also projects that they may be compensating for some emotional insecurity on their own end, trying to assert intellectual “superiority” in some way.
The first option (explaining things simply) might make your job sound easy to a very small minority of extremely uneducated, under-stimulated people, who also have unaddressed insecurities around their own intelligence. But that’s not most humans.
Moderately-to-very intelligent people appreciate how difficult (and useful) it is to explain complex things simply. Hell, most “dumb” people understand, recognize, and appreciate this ability. Honestly, I think not appreciating simple explanations indicates both low mathematical/logical and social/emotional intelligence. Which makes explaining things simply a useful filter for, well… people that I wouldn’t get along with anyway.
With all that said, I prefer to first explain my job in an “explain like I’m 5” style and, if the other party indicates interest, add detail and jargon, taking into account related concepts that may already be familiar to them. If you take them into account, they won’t get bored when you go into detail.
I'm reminded of this dilbert cartoon:
https://web.archive.org/web/20230228154639im_/https://assets...
and I'm reminded of this xkcd about the pattern of lights:
I've often thought how my cat must think I am insane. I sit in from of a medium-sized glowing rectangle, I occasionally look at a small glowing rectangle, then in the evening stare at a really large glowing rectangle.
Other options are :
1) Cats do not really think that much about us at all, except for thoughts like - "oh no! it's about to attack! wait no, it's fine, relax..." or "will it feed me if I shout at it?" or "it's sitting down, perhaps I feel like sitting on it"
2) Their thoughts about us revolve around our weird lack of fur, the strange way we never clean ourselves by licking, and how bad we are at catching small animals to eat.
>our weird lack of fur, the strange way we never clean ourselves by licking, and how bad we are at catching small animals to eat.
Or some of us with our tail on backwards.
I’ve thought the same about our dogs when we stare for hours at “the light box.”
I wonder if it’s anything like what I feel when I watch them sniff the same bush for a seemingly endless amount of time like it’s the most interesting thing in the world.
> Hell, most “dumb” people understand, recognize, and appreciate this ability.
That remark reminds me of all the praise heaped by commenters onto videos that explain complex topics glibly. Like "I've been struggling to understand this for 20 years, until this video", etc.
Except, when, which is often the case in mathematics, there is actual way to reduce the complexity of a topic to be understandable to most people without sacrificing veracity for digestible half truths.
I’m reminded of Feynman’s answer on explaining magnetism.
In other words, ICP were not so far off base when they asked “magnets, how do they work?”
The correct option is to treat such conversations as a protocol with a negotiation at the onset.
SYN ACK
SYN SYN SYN SYN SYN SYN SYN SYN SYN SYN SYN SYN
RST FIN
> With all that said, I prefer to first explain my job in an “explain like I’m 5” style and, if the other party indicates interest, add detail and jargon
It is just your choice. I'd prefer a short answer full of jargon. It gives people the opportunity to clarify what they want to ask. Do they really want to know details? Or they want a rough idea of an answer? Or they just filling silence with small talk?
Though other times, when I really want to talk about it, I'd go with some ELI5 explanation, while watching people, are they interested or not?
> Honestly, I think not appreciating simple explanations indicates both low mathematical/logical and social/emotional intelligence.
It can be. But mostly it is not. People are sending signals by choosing one form of the answer or another, you just need to decode their signals. And it will be better, if you don't jump to conclusions about their persistent psychological traits, based on the first impression.
I think the negotiation signal being sent by "all jargon" is "fuck off". It's not an attempt to gauge what level the other person is using. It's a blank wall, being thrust towards them.
It seems like dumbing it down or immediate heavy jargon with people you don't know are just both equally bad options.
What's wrong with asking their level of experience with the topic?
Sure, with parents you know the level. I'm talking "other strangers" you meet outside of a context where some familiarity would be expected (like at a conference one might assume at least some form of knowledge and ability to just have the other person ask about specific jargon they don't know).
But at the parents dinner party, that other guy may or may not be in your line of work. Just ask them.
> What's wrong with asking their level of experience with the topic?
Nothing. That's precisely the point. Giving a wall of jargon, isn't asking if someone is familiar.
Maybe it's just me but I feel entirely comfortable asking questions like "how much math did you take? do you remember what a derivative is?" and base my explanations on the response. Turns out fine every time so far... and if they don't remember what a derivative is (or whatever) then I just explain it differently no big deal. I'd almost argue it is easier than not asking, but only if I actually care about them understanding the answer.
That is fine. That's not what has been complained about here. That's invitational, not wall of jargon.
- [deleted]
Not exactly a bad thing in my books.
Maybe so, if that is your choice, but it is not giving "people the opportunity to clarify what they want to ask".
> When I meet people who immediately use hyper-specific jargon with strangers,
That is 90% of the professors I asked questions to. If they go full jargon and don't want to explain any of it, they don't want you near them ( or they want you to improve before even having a conversation ).
That just makes them awful professors. They should stick to WWFD (what would Feynman do!)
> what would Feynman do!
The counter-camp is "What would Landau and Lifshitz do?" :-)
---
For those who are out of the loop:
> https://en.wikipedia.org/wiki/Course_of_Theoretical_Physics
"The presentation of material is advanced and typically considered suitable for graduate-level study."
Your default position is distrust and anxiety though. Most people aren't wired that way.
> or assume they’re not emotionally intelligent (because it’s a choice demonstrates little respect for the person they’re addressing)
Intelligence, in the traditional sense, also involves understanding when to give up. Part of "emotional intelligence" is judging whether the other party actually cares about what you're about to say.
>extremely uneducated, under-stimulated people, who also have unaddressed insecurities around their own intelligence. But that’s not most humans.
This isn't going to be most humans you encounter if you're in the HN demographic, but that's a bubble. It does describe most people in the world.
This is, in a word, nonsense.
> When I meet people who immediately use hyper-specific jargon with strangers, I either distrust them, or assume they’re not emotionally intelligent (because it’s a choice demonstrates little respect for the person they’re addressing).
For me, it's quite the opposite: such a choice demonstrates that they their prior is that I'm sufficiently smart and knowledgable to be likely able to understand this explanation - which I rather consider to be a praise. :-)
I think "with strangers" is the important bit. If a nuclear engineer is talking to some lay person and uses hyper specific jargon, then grandparent is correct. If you've established a shared competency with the person, and are therefor no longer total strangers, that's totally different.
True, but however, there are times when I just really need to talk about the extremely detailed bits of some problem I'm thinking about - just the act of speech is really needed; I find this super annoying in other people, but forgivable because I also experience it. I have heard so much about minutiae from my kids that I have to force myself to just semi-actively listen to. My wife has to hear so many things that annoy her as well, when I don't get enough chattering out to co-workers or colleagues.
"Everybody needs a rubber duck."
Sometimes, explaining your issue to a random person leads you to a solution. They don't even need to have any experience with the same or a similar issue; indeed, sometimes it's better if they don't! Often turns out you don't need someone who can respond, so explaining to an object like a rubber duck will do.
>You can give a quick explanation in terms they understand, which makes your job sound easy and makes them wonder how anybody gets paid to do it.
What is the problem with this?
Most jobs, when simplified, sound like "anybody can do it". I think it's generally understood among adults who have been in the workforce that, no, in fact anybody cannot do it.
There is no problem with it, but I assume there are many people who will look upon you favourably if they think you do a highly skilled job. While many of us may not care to impress those people, there are certainly those who do (possibly people with similar attitudes who care more about validation from people who think like them)
A somewhat ungenerous characterization of the attitude may be something like the Rocket Scientist vs Brain Surgeon sketch - https://www.youtube.com/watch?v=THNPmhBl-8I
But we should also acknowledge that there's an entire culture built around valuing people and their time relative to one's perception of their "importance", that this culture can influence one's earning potential and acquisition of material possessions, and that many people do care about things like "seeming important" or moving upwards in this hierarchy as a result.
I think which direction you choose is about knowing your audience. As you mentioned, different people value different things and humans often want to present a different view of ourselves to different people at different times.
The way I think about it is this. There are roughly two groups of people:
- Some people will not care / be dismissive of what I have to say. I probably don't want to talk to these people much.
- Some people will be interested! I probably will like these people.
If I use technical jargon, I am optimizing to impress people I don't really care about impressing - and I will be pushing away the people that I would actually be interested to spend time with.
If I speak respectfully, i.e. the simple explanation, it will resonate more with the people I like. I will push away the people who don't care, but I didn't really want to talk with them anyways.
I don't see what's hard about threading the needle, or maybe I'm completely lacking in EQ
"I'm a mathematician, I study how shapes fit together, which surprisingly, is being used for new methods of secure communication by so and so university, but I just love the math"
Or “I’m a mathematician. I try really hard to find things I can prove that have no practical application. But frustratingly people keep finding important practical applications for my work.”
> No one has yet found any war-like purpose to be served by the theory of numbers or relativity or quantum mechanics, and it seems very unlikely that anybody will do so for many years. - G.H.Hardy, Jan 1940 > A few decades later, we stand waiting for nuclear bombs guided by GPS to be launched when the cryptographic auth certificate is verified. So it goes.
I choose the worst of all options and go into excruciating detail.
Thereby minimizing how often anyone asks you - which makes that the best long-term option?
That would only work if you were getting repeat inquiries from the same person. Otherwise it's just the longest possible option for each new inquiry.
I always opt for excruciating detail because it's what I enjoy the most.
> That would only work if ...
Sounds like none of the people you answered, in excruciating detail, cared to warn other people about what would happen if they asked you.
It really can go both ways. Was told that "Ask baobun about hacking when you're high" came recommended.
Ahh! I didn't think about the word-of-mouth. Good call.
My wife's eyes just gloss over. Maybe I should try with some other test subjects.
One of the classical assessments in strategic behavior is "be worse than your roommates at chores so they do them, but not so bad they kick you to the curb."
I kinda love doing the quick+easy explanation... And especially in professional contexts.
"I teach computers what sounds different aminals make."
As a person who uses the Merlin app regularly, I appreciate this field of study.
Great pickup line.
> You can give a quick explanation in terms they understand, which makes your job sound easy
This is always the right answer. It is the only answer that respects the listener and contains a seed to further conversation.
> You can give a quick explanation in terms they understand, which makes your job sound easy and makes them wonder how anybody gets paid to do it.
What's wrong with this? Making it look easy is why you get paid for it.
The latter option always comes across as rude. It's a very clear 'piss off you insect'
> The latter option always comes across as rude. It's a very clear 'piss off you insect'
To me, it rather tells: "I consider you to be likely to be sufficiently smart and knowledgable to understand this topic if you put in some effort: do you want to learn some cool stuff which otherwise would demand a lot of literature research to learn? And since I already hinted that I consider you to be smart and knowledgable: would you like to teach me some cool, complicated stuff, too?"
That would be nice.
But it is by far more common that it means "piss off you insect".
I think you can explain the product you work on rather the what you actually do.
I personally say I work on Bluetooth support for Google Home assistant devices. "It's like Alexa, but Google.
Even if you work on some absurdly down stack thing, this seems to work. You work on making sure the internet is as fast as possible, or files are stored in the cloud properly, or the graphics on your computer are displayed correctly.
I once told my dad that if the subject of my thesis was something I could easily explain then it wouldn't be interesting enough to do a PhD in. I said it half-jokingly and he laughed about it, but he stopped asking me what I'm studying after that so maybe he did take it more seriously.
There’s something bittersweet about that moment when someone you love stops asking about your research. It’s a quiet kind of respect, but also a reminder of the communication gap academia often creates.
Introduce him to the annual Dance Your PhD contest:
https://duckduckgo.com/?q=dance+your+phd&ia=videos&iax=video...
Of course, there is the unstated second part that you really aren't qualified for a PhD until you can explain it simply.
i once got excited to explain to my father what i did at a research lab after grad school. he listened patiently for about 30 minutes then he said “oh, so you build software for big business?”
Hard to explain doesn't make it interesting either.
> There are three choices
There is another:
Give away as little information as you can about it.
Don’t say or agree that it’s secret or that you can’t talk about it- just be tight-lipped, and don’t divulge.
If you do it right, you will seem mysterious.
If you do it wrong, they probably won’t talk to you much again.
Win-win.
— Hi, and what do you do?
— What’s your security clearance?
>You can explain what you do and why it's important in terms they understand, but it'll take so long they'll get bored and wish they hadn't asked.
Yes, don't fall into this trap. The other two options are still better. Everyone says, "no, no, I really want to know" and then tunes out two minutes later; then four minutes later they start doing the George Carlin lean: "Surgery! I am having my ears sewn shut!".
I work at many levels and on many different projects, so usually I give a very simple explanation of the most interesting one, in very simple terms, and add, 'that's a small part of my job'.
People that are interested can ask either to give more details on what I have explained, or what about the rest. If they are not interested, they say something and I usually ask what about them, no hard feelings.
It works smoothly for me.
I don't have that problem ("I work with computers / I am a computer programmer") but I usually follow with "I'm a race driver. I drive the car as fast as I can, I don't change the tires nor the oil in it" when I get the usual "can you fix my computer?" request.
For reasons that I care not to ask people get seriously annoyed by that.
I like that analogy for the simple reason that I imagine most race car drivers do in fact have opinions about tires and oil and know how to fix them. It's just not the main part of their job. Similarly, you probably would be a lot better at fixing computers than a layman.
There's more choices than three.
Eg you can focus on what you actually do, or you can focus on the benefits you bring to other people.
Or tell them about the bit of the job they understand. "I teach maths to adults".
I think about things and then type in stuff that makes them work better.
I'll bite: What is your job?
Chief Dexitroboper.
Really? When I see that all I think is it's one of "them" - the kind that takes some kind of perverse pleasure in needlessly mystifying, complicating, and obfuscating things as much as possible - especially the trivial.
Blowing smoke around simple things to gatekeep them is not impressive and not cute.
If you can't explain something in simple terms, you don't understand it well enough
Some ideas are too complex to explain accurately in simple terms.
You can give someone a simple explanation of quantum chromodynamics and have them walk away feeling like they learned something, but only by glossing over or misrepresenting critical details. You’d basically just be lying to them.
Quantum Mechanics is the example of a subject where supposed experts don’t really understand it either and hence can’t explain it adequately.
Also, it’s hilarious to get comments like this voted down by non-experts who assume this must be an outsider’s uninformed point of view.
I have a physics degree and I studied the origins and history of quantum mechanics. Its “founding fathers” all admitted that it’s a bunch of guesswork and that the models we have are arbitrary and lack something essential needed for proper understanding.
Take for example entanglement.
The math that describes it is known precisely. Specific implications of this are known. There's no information transfer, there's no time delay, etc.
And yet lay people keep incorrectly thinking it can be used for communication. Because lay-audience descriptions by experts keep using words that imply causality and information transfer.
This is not a failure of the experts to understand what's going on. It's a failure to translate that understanding to ordinary language. Because ordinary language is not suited for it.
> Its “founding fathers” all admitted that it’s a bunch of guesswork and that the models we have are arbitrary and lack something essential needed for proper understanding.
We don't have a model of why it works / if there's a more comprehensible layer of reality below it. But it's characterized well enough that we can make practical useful things with it.
> This is not a failure of the experts to understand what's going on.
> We don't have a model of why it works / if there's a more comprehensible layer of reality below it.
Counterpoint:
You’ve just admitted they don’t understand what’s going on — they merely have descriptive statistics. No different than a DNN that spits out incomprehensible but accurate answers.
So this is an example affirming that QM isn’t understood.
QM isn't less well understood though than Newton's mechanics. Neither cover the "why". But both provide a model of the world, the model (!) is very precisely understood and it matches observations in certain parts of reality. Like all reasonable scientific theories do. They have limits, and beyond those limits they don't apply, but that doesnt mean they are not understood. It's reality that is not sufficiently well understood and by coming up with more and more refined models/theories, we keep approximating it, likely without ever having a "fully correct" theory encompassing everything without limits. (But that's ok.)
The only descriptive / empirical parts is the particle masses.
But it sounds like your objection is that reality isn't allowed to be described by something as weird as complex values that you multiply to get probabilities, so there necessarily must be another layer down that would be more amenable to lay descriptions?
That’s not my point, nor close to what I said.
My point is that their models are fitted tensors/probability distributions, often retuned to fit new data (eg, the epicyclic nature of collider correction terms) — the same as fitting a DNN would be.
Their inability to describe what is happening is precisely the same as in the DNN case.
Actually it is just the opposite. QED is comprehensive and, as far as we know, accurate.
But it is impractical to use in most situations so major simplifications are required.
The correction factors that you mention are the result of undoing some of those simplifications, sometimes by including more of the basic theory and sometimes by saying something like "we know that we ignored something important here and it has to have this shape but we can only kinda sort measure how big it might be because it's too hard to actually calculate".
If you have a very small neural network, you can fully understand and explain how it works.
As you increase the detail of a description, it reaches a point where nothing is missing.
As I pointed out, eg, the high number of correction terms when trying to tune the model to actual particle accelerator data is evidence that our model is missing something. (And some things are plain missing: neutrino behavior, dark matter, dark energy, etc.)
In the same way that a high number of epicycles was evidence our theory of geocentrism was wrong — even though adding epicycles did compute increasingly accurate results.
The standard model has ~20 parameters (depending on what exactly you include as 'the' SM) and it predicts hundreds of thousands of data points.
> As I pointed out, eg, the high number of correction terms when trying to tune the model to actual particle accelerator data is evidence that our model is missing something. (And some things are plain missing: neutrino behavior, dark matter, dark energy, etc.)
This is rather a problem of the standard model. Physicists will immediately admit that something is missing there, and they are incredibly eager to find a better model. But basically every good attempt that they could come up with (e.g. supersymmetric extensions of the standard model; but I'm not a physicist) has by now (at least modtly) been falsified by accelerator experiments.
The comment you originally replied to was about entanglement, not the entire standard model. The math there is very simple, not built on correction terms.
- [deleted]
... So it's about not being able to observe short-lived particles directly, and having to work backwards from longer lived interaction or decay products? Or about how those intermediate particles they have to calculate through also have empirically-determined properties?
Most of that is measured corrections, not a theoretical model.
Entanglement is just a statistical effect in our measurements — we can’t say what is happening or why that occurs. We can calculate that effect because we’ve fitted models, but that’s it.
Similarly, to predict proton collisions, you need to add a bunch of corrective epicycles (“virtual quarks”) to get what we measure out of the basic theory. But adding such corrections is just curve fitting via adding terms in a basis to match measurement. Again, we can’t say what is happening or why that occurs.
We have great approximators that produce accurate and precise results — but we don’t have a model of what and why, hence we don’t understand QM.
> Entanglement is just a statistical effect in our measurements — we can’t say what is happening or why that occurs. We can calculate that effect because we’ve fitted models, but that’s it.
Bell's theorem was a prediction from math before people found ways to measure and confirm it. A model based on fitting to observations would have happened in the other order.
> A model based on fitting to observations would have happened in the other order.
We’d already had models which said that certain quantities were conserved in a system — and entanglement says that is true of certain systems with multiple particles.
To repeat myself:
> Entanglement is just a statistical effect in our measurements — we can’t say what is happening or why that occurs.
Bell’s inequality is just a way to measure that correlation, ie, statistical effect — and I think it’s supporting my point the way to measure entanglement is via statistical effect.
ER=EPR is an example of a model that tries to explain what and why of entanglement.
There's nothing wrong with that: https://en.wikipedia.org/wiki/Lie-to-children
Reminds me of the old videos on the Mill CPU architecture. There is multi hour long video about “the belt”, a primary concept in understanding the Mill architecture and instruction scheduling. It’s portrayed in the slides as an actual belt with a queue of items about to be processed, etc.
Only in the end to reveal the belt is truely conceptualized and does not formally exist. The belt is an accurate visual representation and teaching tool, but the actual mechanics emerge from data latches and the timing of releasing the data, etc.
I thought it was helpful.
Is this an asynchronous architecture CPU?
It's not. I'm curious what gave you that idea, though?
The belt moves once per cycle, if that wasn't clear? He says the word "cycle" (and measures latency in cycles) a lot.
That's how you get a whole population imagining mitochondria as puffy gelatinous beans, instead of network around other organelles.
https://www.nature.com/immersive/d41586-025-00269-y/index.ht...
To me, every profession—from software engineering to farming—has its complexities, yet most professionals can explain what they do in clear terms. When academics say they can’t offer a basic explanation, it often feels like an attempt to protect their status or avoid the effort—if not a kind of intellectual arrogance. Yes, the topics are challenging—you don’t need to throw in quantum buzzwords to convince me—but simplifying your work isn’t “dumbing it down”; it often sharpens your own understanding too.
I encounter this idea too much..the idea that complex topics can always be explained in a way to make everyone understand it...and that just isn't true. There is usually a point on any topic where further reduction/compression is no longer lossless. Yes, I think the analogy of image compression works pretty well. Lossless compression can only go so far. Further reduction introduces loss, but the image may still be understandable, but at a certain point, the loss from compression prevents understanding of the image, and may even mislead (Is that a bear, or uncle Robert?).
If you have such an opinion, explain some advanced papers of Peter Scholze to me.
'It's the study how the particles that make atoms interact... it's fiendishly complicated'
I personally think of this in terms of giving directions.
It's easy to give directions to somewhere near where you currently are -- "Just head down the road, it's the second left, then 3 doors down".
When giving directions to a far-away place you either have to get less accurate "it's on the other side of the world", or they get really, really long. Unless of course they already know the layout of the land -- "You already know Amy's house, over in Algebra Land? Oh, then it's just down the road, fourth left, six doors down".
People often seem cleverer because they know the layout of some really obscure land, but often it's just because people have never been anywhere near it. I have a joke about my research where I say, "A full explanation isn't that hard to explain, it's just long. About 4 hours probably. Are you interested?" So far, I've had 3 people take me up on that, and they all seemed to have an understanding once I'd finished (or, they really really wanted to escape).
- [deleted]
Simple terms need not be short terms.
Huh; now want to write a Supercalifragilisticexpialidocious song for my research topic.
As one must.
And that’s why Feynman was always happy to explain how magnets work!
Feynman was happy to explain why he couldn't explain how magnets work!
Not every subject has simple explanations.
- [deleted]
A horse is just a bunch of chemicals in a skin sack. Gee, I understand it!
Hmmmm, what might Feynman say about a horse?
So, what's a horse? Well, you look at it: it’s this big animal, standing on four legs, with muscles rippling under its skin, breathing steam into the cold air. And already — that’s amazing. Because somehow, inside that animal, grass gets turned into motion. Just grass! It eats plants, and then it runs like the wind.
Now, let’s dig deeper. You see those legs? Bones and tendons and muscles working like pulleys and levers — a beautiful system of mechanical engineering, except it evolved all by itself, over millions of years. The hoof? That’s a toe — it’s walking on its fingernail, basically — modified for speed and power.
And what about the brain? That horse is aware. It makes decisions. It gets scared, or curious. It remembers. It can learn. Inside that head is a network of neurons, just like yours, firing electricity and sending chemical messages. But it doesn’t talk. So we don’t know exactly what it thinks — but we know it does think, in its own horselike way.
The skin and hair? Cells growing in patterns, each one following instructions written in a long molecule called DNA. And where’d that come from? From the horse’s parents — and theirs, all the way back to a small, many-toed creature millions of years ago.
So the horse — it’s not just a horse. It’s a machine, a chemical plant, a thinking animal, a product of evolution, and a living example of how life organizes matter into something astonishing. And what’s really amazing is, we’re just scratching the surface. There’s still so much we don’t know. And that is the fun of it!
Sounds like an LLM's impression of Feynman.
It does seem that way, doesn't it. Feynman passed away 37 years ago, so he wasn't available for this.
How simple? Simple to who?
The quip you're referring to was meant to be inspirational. It doesn't pass even the slightest logical scrutiny when taken at its literal meaning. Please. (Apologies if this was just a reference without any further rhetorical intent though.)
It's like claiming that hashes are unique fingerprints. No, they aren't, they mathematically cannot be. Or like claiming how movie or video game trailers should be "perfectly representative" - once again, by definition, they cannot be. It's trivial to see this.
I have my own micro business where I make equipment for high energy physics machines.
I have yet to figure out a way to tell people what my business is in a way that is even slightly accessible. Everything about it is so esoteric and multiple steps removed from regular life. It's not necessarily complex, it just contains a ton of details that the average person has no familiar contact with, and don't really have everyday analogues.
Isn't "I have my own micro business where I make equipment for high energy physics machines" a good description already?
> I make equipment for high energy physics machines
> I have yet to figure out a way to tell people what my business is in a way that is even slightly accessible.
You ... just did? In a remarkable short, concise, and very accessible way. I can ask as many follow up questions as I want and we might even have an engaging conversation. Sounds interesting!
It doesn't really tell you much, and frankly my audience is mostly non-tech people. And no doubt some people really are curious and keep asking questions, but most people you can kinda see their head uncomfortably spin.
I also obfuscated it a bit by giving the most general name just for privacy reasons since not many people do it. But rest assured it is a "Retro Encabulator" type machine, and as you add details it just becomes more and more alien.
This is not at all what I do, but its similar esoteric-ness to "I make differential gear sets for calibrating ion trap interferometry systems". A collection of words where every one of them the average person struggles to place.
Help me that you're not a doctor a lawyer accountants software engineer working for a large company. It tells me you're a small business owner and you work on advanced things. You're not manufacturing knick knacks or toys.
Really if we're at a party that's more than enough unless I want to ask you more and you want to talk more about it. If you were a lawyer I'd probably ask what area of law that I probably stop and talk about something else. So I agree with others that you said was a very good distillation of what you do to the level that most people probably care about
"I have a small business that creates parts for machines used to do physics research" is perfectly understandable, though.
My cousin has his own metrology business, and it took me a long time before I understood how he was doing so well financially. Kinda get it now.
I make gear for machines that throw energy beams/lightning/lasers?
I just say “I work with computers”. I get the nod of “oh right nice” and that’s it. Done.
> I just say “I work with computers”.
This is a suitable description of possibly 70 % of all jobs.
At least in the case of sphere packing it's closely related to some core problems in information theory that helped make the Bell phone system so reliable.
(not sure about convex shapes)
Yeah I'd definitely explain that one as "I study ways to make wifi faster", doesn't cover all the nuance, but it's definitely better than the alternative.
Convex shapes, well, annoyingly it's too broad. It has way more applications than sphere packings but it's hard to pick a good example. It's like trying to explain you design screwdrivers to someone who doesn't know what a screw is.
There is a way to explain to neophytes and it's generally to be more emotional problem-solving and intuitive, and less logical or scientific. There's a toxicity that can rise up in talking in a seemingly over-specific manner which puts people off.
Explain it from the perspective of, "well, in order to get XYZ done, we are frustrated by it being hard, so we make an easy guess .. we try thinking about the problem in this crude way way because that's easy to think about, and then we make ABC because we know about ABC's ... and we are excited when using it gets us closer to working than anything else we've tried before".
Emotion-laden explanations are a viable way to explain to non-techs. They may be more comfortable thinking emotionally, whereas we are steeped in the logic and sometimes mathematics of our practice. So we must reintroduce emotion into the explanations.
It worked for me, explaining to my family, they followed on and actually understood.
I describe myself as a plumber but with systems for moving around masses of data instead of water.
I usually struggle not with the “what is it you do?” question but with the following “how is it useful/applicable?”
How do I concisely describe the long chain between a fundamental research and something tangible?
While making it clear that packing spheres, which are also shapes that don't jut inwards, is a completely different field.
- [deleted]
I practiced with my wife. Now I can describe my job as a service for making services.
“I’m an electron wizard. I write spells and magical constructs appear on the mirror slate”
betjeman's delightful poem "executive" had a great humorous take on this:
You ask me what it is I do. Well, actually, you know,
I'm partly a liaison man, and partly P.R.O.
Essentially, I integrate the current export drive.
And basically I'm viable from ten o'clock till five.
"You know what?"
convex hulls your car
shapes that exist on higher dimensions we can't mentally comprehend.
FTA: “in 100-dimensional space, his method packs roughly 100 times as many spheres; in a million-dimensional space, it packs roughly 1 million times as many“
Nice example of how weird large-dimensional space is. Apparently, when smart minds were asked to put as many 100-dimensional oranges in a 100-dimensional crate as they could, so far, the best they managed to do was fill less than 1% of its space with oranges, and decades of searching couldn’t find a spot to put another one.
“Fill less than 1% of its space” becomes a very counter intuitive statement in any case when discussing high dimensions. If you consider a unit n-sphere bounded by a unit cube, the fraction occupied by the sphere vanishes for high n. (Aside: Strangely, the relationship is non monotonic and is actually maximal for n=6). For n=100 the volume of the unit 100-sphere is around 10^-40 (and you certainly cannot fit a second sphere in this cube…) so its not surprising that the gains to be made in improving packing can be so large.
> (Aside: Strangely, the relationship is non monotonic and is actually maximal for n=6)
For this aside I crave a citation.
When n=1 the sphere fit is 100% as both simplex and sphere are congruent in that dimension. And dismissing n=0 as degenerate (fit is undefined there I suppose: dividing by zero measure and all that) that (first) dimension should be maximal with a steady decline thereafter thus also monotonic.
This looks to have been a conflation by the GP between the volume of the unit sphere itself and its ratio to the volume of its bounding cube (which is not the unit cube.) The volume of the sphere does top out at an unintuitive dimension, but indeed the ratio of the two is always decreasing - and intuitively, each additional dimension just adds more space between the corners of the cube and the face of the sphere.
You don't need to involve the hypercube at all. You can just look at the volume of a hypersphere (n-ball). The dimension where the maximal volume of the n-ball lives depends on the radius, and for the unit n-ball, the max is at 5D, not 6D. As D->inf, then V->inf too.
This relationship doesn't happen to the hypercube btw. Really, it is about the definition of each object. The volume of the hypercube just continues to grow. So of course the ratio is going to explode...
As an extra fun tidbit, I'll add that when we work with statistics some extra wildness appears. For example, there is a huge difference between the geometry of the uniform distribution and the gaussian (normal) distribution, both of which can be thought of as spheres. Take any two points in each distribution and draw a line connecting them and interpolate along that line. For the unit distribution, everything will work as expected. But for the gaussian distribution you'll find that your interpolated points are not representative of the distribution! That's because the normal distribution is "hollow". In math speak, we say "the density lies along the shell." Instead, you have to interpolate along the geodesic. Which is a fancy word to mean the definition of a line but aware of the geometry (i.e. you're traveling on the surface). Easiest way to visualize this is thinking about interpolating between two cities on Earth. If you draw a straight line you're gonna get a lot of dirt. Instead, if you interpolate along the surface you're going to get much better results, even if that includes ocean, barren land, and... some cities and towns and other things. That's a lot more representative than what's underground.
Citation(s):
Urgh you’re right. I was being dumb and am now ashamed
I’m familiar with this example of hyper-geometry. Put more abstractly, my intuition always said something like “the volume of hyper geometric shapes becomes more distributed about their surface as the number of dimensions increases”.
There's a great 3blue1brown video that demonstrates this unintuitive result in a relatively intuitive way: https://youtube.com/watch?v=zwAD6dRSVyI
This doesn't hold true for 2 and 3 dimensions, though.
If it holds for 10 or 20 dimensions, the consequences are still pretty important.
It's rather crazy that we humans can't really even intuit about a single extra dimension. Or even a single fewer! There's a lot of people who will say that they can visualize things in the 4th dimension but I've yet to find someone who can actually do this. This includes a large number of mathematicians (it's never the mathematicians that claim this...)> how weird large-dimensional space is
I really like the animation in this Math Overflow post[0], because it has a lot of hidden complexity that most people don't think about. The animation is actually an illusion, and you are "hallucinating". That top image projecting a cube down onto a plane? Well... that isn't a cube. We've already projected the cube into 2D! Technically this is 3D. But the 3rd dimension isn't a spacial dimension, it is a time dimension. Which itself is a helpful lesson in learning about the abstraction of dimensions! So we hallucinate a cube, rotating, and then see the projected image on a plane, which we hallucinate as a square that isn't skewed but instead has depth. This is all rather wild in of itself.
The truth is that we struggle to imagine 2D! And most people will claim to be able to visualize 2D and the claim will go uncontested.
If you haven't read Flatland[1], I'd encourage everyone to do so. A lot of people get it wrong. They read it as an analogy 1 dimension down. Where we 3 dimensional creatures are analogous to the 2D creatures and a 4D creature would be as baffling as a 3D creature is to the Flatlander. While that is true, there is a trick being played on you. You think understanding 2D is really easy. But I guarantee you what you're visualizing is inaccurate. Frankly, the book isn't perfectly accurate either.
But really put yourself in the Flatlander's shoes. In a real Flatlander's shoes, not the ones of the book. Be the Square Flatlander and imagine yourself looking at a Triangle. What do you see? I'm betting it is a line? But this is incorrect. You've given it thickness, you've given it a third dimension. Try this again and again, adding more depth and challenging yourself to imagine a real Flatland. You'll find you can't.
Instead, we can visualize and reason about a 2D space embedded within 3D. You might say I'm being nitpicky here, but if I weren't then it would be perfectly fine to say that this[2,3] is a 4-dimensional hypercube instead of a representation of a 4D hypercube.
I actually think understanding this goes a long way to help understanding very high dimensions. If you are forced to face the great difficulty of accurately visualizing one more or one fewer dimension, you are less likely to fool yourself when trying to reason about much higher dimensions.
And as Feynman once said:
[0] https://math.stackexchange.com/a/2286226The first principle is that you must not fool yourself and you are the easiest person to fool.
[1] http://www.geom.uiuc.edu/~banchoff/Flatland/
[2] https://en.wikipedia.org/wiki/Tesseract#/media/File:8-cell-s...
[3] Good video of Carl Sagan where he holds a 3D projection of the hypercube. The shadow. But anything I show you has to be embedded in 2D... He picks it up at 6:20 https://www.youtube.com/watch?v=UnURElCzGc0
Neat. I spent a month trying to use sphere packing approaches for a better compression algorithm (I had a large amount of vectors, they were grouped through clustering). Turned out that theoretical approaches only really work for uniform data and not any sort of real-world data.
EDIT: groped -> grouped
The usual trick is to use domain-specific knowledge to translate that asymmetry to uniformity.
E.g.: Suppose the data has high-order structure but is locally uniform (very common, comes about because of noise-inducing processes). Compute and store centroids. Those are more uniform than your underlying data, and since you don't have many it doesn't really matter anyway. Each vector is stored as a centroid index and a vector offset (SoA, not AoS). The indices are compressible with your favorite entropic integer scheme (if you don't need to preserve order you can do better), and the offsets are now approximately uniform by assumption, so you can use your favorite sphere strategy from the literature.
Intelligence is compression
You really shouldn't grope your vectors.