I would think that by now that shouldn't even be up for discussion - much less for programming where your objectives, besides achieving a calculation or a side-effect, are also that your code be intelligible to other human beings. Even in assembly you have symbols for move, jump, etc.
And no, different people have different ways of thinking, not everyone has the same combination of nature and nurture to be completely comfortable with pure abstract mathematical notation - and for most part they don't need to. When you assign fancy greek letters as symbols you're also labelling them, so why not label them with something that a person learning might recognise.
Outside of teaching people that aren't familiar with it, yeah, sure, use all the numerical elegance you can muster (and I would still argue that even there it's still detrimental if the objective is sharing knowledge as widely as possible).
Or do people here really think that nobody has ever tried to make a math textbook with lengthier names and descriptions? It isn't used since it doesn't make things better, it makes them worse.
We can either believe that there's just a big percentage of people that will never be able to grasp beyond arithmetic (mathematically dumb) or that perhaps we aren't teaching things in the best way possible?
When I say using descriptive/relatable labels, is in the context of a relatable problem. I also think this is common, in the very first levels of introducing maths for small children it's a normal procedure. At some point between that and more advanced topics it seems to jump off and the conclusion seems to be "Many students fail to master requisite concepts before advancing to more complex ideas, leaving them ill-prepared to succeed in higher level Science, Technology, Engineering, and Mathematics (STEM) coursework.". Of course it's the students (usually kids) that fail, not the very smart lecturers and teachers. At every point in time probably people think of the way they're doing something as the most sensible or best way of doing it.
I think there was quite a leap when programming let go of pure mathematical notation to more regular language likeness - it seems many at the time voiced their opposition to that too.
Not long ago I spent some hours chasing around a problem where had the authors I encountered tried to explain it using more descriptive problems I would have grasped it in minutes, because it was really basic. But yeah, maybe it sounds really smart when it's shrouded in jargon, symbols and meanings that only someone immersed in that field of study would understand.
https://www.youtube.com/watch?v=Qhm7-LEBznk
The problem here is that she don't know what speed is. She knows a lot of formulas, but not what speed actually is. That is a typical student, if you add speed in a formula you will make them confused and the problem will get harder.
The word problem was basically the same as in the video. If you're moving 20 miles/hour how long will it take to go 40 miles. (honestly, this was 20 years ago ... the problem probably said "20 MPH" ... it wasn't a very good textbook)
I read the problem to her, similarly to how the guy in the video was trying to explain. "If you are going 20 miles... per hour..."
She was in drivers ed at the time, so I tried talking about her speedometer and "MPH and how that stands for Miles Per Hour"...
Eventually I wrote it down for her as a fraction "20 miles / 1 hour" and not only did she figure it out but she also said "Oh my god, that's what MPH means? I thought that was just a number I had to match with the speed limit signs!"
One of the toughest parts of teaching is figuring out where you need to start (for each student). The thing that gets a student stuck might not even be related to the material... they may have an incorrect preconceived notion that you're not aware of so they think they know what MPH is, but it's actually something completely different, so you are not effectively communicating with each other because all the words you are using have different meanings.
What I am saying is First, if student don't even understand what is carAccerleration or carSpeed is, then how do you expect them to understand the X and Y term?
Second, to explain an example, you may not use carSpeed or anything related to it at all, but why use X and Y while there are so many better names out there. It really depends on the context of the example trying to show. So my point is using carSpeed or carAccerlation as programming naming technique bad? Yes, it's bad. But using greek terms to show a student who are really bad at understanding things comes even worse. How we can explain them what is alpha, what is beta, etc
I am not an official teacher at any school, but I volunteered to an educational organization to teach students about science experiments. The odd is there is a huge gap in knowledge in ONE class, students range from 6th grade to 9th grade. Student of 6th grade in class don't even know what is physics and chemistry (all stuffs they know is adding and substracting). My job is explaining to them what electromagnetic field is and how the tesla coil works. That's come to my point, you can't just throw to them a bunch of equations and tell them it is it. I had to solve this by breaking the term down into smaller pieces and didn't talk about any equations at all. After that, could I expect them know how to solve physics problems? Of course, it's not. But at least they had a push, and if you want someone to move forward, a small push is what they need (Newton's first law related). That is the 'A-hah' moment.
One more point, if you have read 'A Brief History of Time' of Stephen Hawking, you'll see he barely used any complicated terms or equations in his book (he did use, but not much), he just explain things and break it down into small pieces so even non-physiscal peoples will understand.
And in conclude, if it's for generalize things, then an equation with greek terms is needed. However, to explain things to student who are bad at math and really need help, there is so many better ways to name terms in math examples instead of using greek letters.
You can apply context to any generic abstraction/formula, otherwise the math is useless, by definition.
Teaching people effectively requires context.
I hope I don't have to read your code with single letter variables everywhere then! There's a reason that's considered a bad practice. Math gets a pass, why?
I'm not sure that this kind of snark is helpful if you want to teach something.
My point is precisely to make things as easy as possible, not harder! Variables are just slots. How would you rewrite the following using "meaningful" variable names?
The two solutions of aXX+bX+c = 0 are X=(-b+√(bb-4ac))/2a and X=(-b-√(bb-4ac))/2a ?
Any "meaningful" names that you could assign to the terms X, a, b, c would depend heavily in the context. You would convert this equation into an unrecognizable monstrosity. But this equation appears in many different, completely unrelated contexts! The main point of math, I'd say, is that no matter what is the context, the equation is always one and the same and it is solved in exactly the same way. Thus it pays off to have variable names as meaningless as possible.
You would convert this equation into an unrecognizable monostrosity."
For any beginner this is a unrecognisable monstrosity.
Having real names for the variables can give them something to hold on. Something they can relate to. So it makes sense to their brain.
And later on, you can abstract it - and they are fine with it and see the benefits. (I still want programming variable names to be as descriptive as possible)
You (and probably everyone else around here) are used to abstraction - a beginner to math is not!
(and sadly, most people are even after 12 years of schoolmath still beginners in math)
And the focus on abstraction is a huge wall, making everything harder than it needs to be.
" Thus it pays off to have variable names as meaningless as possible. "
I agree that this is very helpful to achieve, when you are dealing with plain math only. But I think this thinking actually lead to lots of real world harm - when variables are not meaningless factors in math - but representing real persons. Which is forgotten quite often, if some buerocrat for example just sees them as a "meaningless variable" and treats them like this. But in reality this can mean, someones existence just got crushed.
Can you rewrite this same equation using "real names" so that it becomes less monstrous? I don't think that's possible, but maybe you have something in mind.
I recognize it exactly as this: as some abstract equations - but nothing more. (am I supposed to recognize them?)
There is of course no real point in adding names later on. At least not without context.
I would start with a real world example. And then - yes have the equations with long names.
And then after that - have the equation as abstract plain math - in the shape you posted it. But not starting with it.
And like I said: nothing wrong with using x, y and z - when teaching und using abstract math.
My point was and is, that this should come later. After the real world examples.
I don't think so, as you can embed allmost any math concept in a real world context. Then the numbers get meaning - then the brain accepts dealing with it easier.
The first time I had real fun with math, was when I dived into computergraphic and had to come up with equations for various vector related stuff.
Suddenly there was meaning to it - the equations provided real benefit. With great visual results. So I had fun improving my equations with pen and paper. I never had that doing abstract math. Only slight relief when some equation finally solved, but it remakned abstract and meaningless.
So this is where I would start: a real world problem - and then to solve it, show how abstraction helps. And all the various needed math concepts along the way.
But starting with abstractions or focusing too much on them, just creates more mental blocks. I certainly had some with math - and I liked science from being very young. For common persons it is much worse. Just have a look how the common people discuss numbers related to covid for example ..
Not without adding a lot of complexity. What I meant is that the concepts taught in maths very rarely map directly to any real world problems. GPU programming is a good example, it uses a lot of vector related maths but the leap from not knowing about vectors to GPU programming is huge and not a good way to learn the subject, since you would have to think both about the complexity of GPU's and graphics and about the vector abstraction at the same time. The reason you had fun doing GPU programming is because you already knew about the interface of vectors so you had no problems working with them.
Actually no.
I had to relearn them pretty much completely, as I forgot all the abstract lessons before. But I had fun doing so. Because my brain saw real world use.
My suggestion is to first teach the generic concept wrapped in context that's more relatable to the student. Similar to code, it's easier to understand the purpose of a variable when you understand the surrounding context as well.
For your formula above, you could define the axes as something meaningful. Say, e.g. instead of A, B and C you have Supply, Demand and Price.
If I read a formula such as:
Demand = 100 + 50Price
Supply = 50 + 20Price
It's easier for somebody to relate to utility of the math than something like:
A = 100 + 50C
B = 50 + 20C
Of course, the math is exactly the same, but you give the student something to relate to.
Now, Supply/Demand is not something the average person can relate to. Obviously context has something of a cultural and familiarity bias. But there are examples that are likely to be close to universal. I use economics here, just because it's a discipline I'm familiar with :)
I don't advocate teaching strictly in contextual examples, but to use them first to provide ELI5 level introduction to concepts. The utility behind the math becomes more clear.
Of course, this is just my take/experience. I spent the majority of time in college skipping class and self teaching, and I discovered that the fastest approach to learning something new is to start at highest level of abstraction and work down. Usually I would learn concepts from resources other than the textbook, as they conveyed information more effectively.
Trying to learn concepts "bottom up" rather than "top down" works, but is less time efficient.
No, you give the student an extra problem they need to solve: Figure out what the hell supply and demand has to do with price. Understanding that isn't expected of high schoolers and teaching it isn't a part of mathematics.
History shows there are no intuitive equations outside of basic counting and summing. Even the concept of rate of change weren't explored before the 17th century, before then people had very ridiculous views on what equations physics uses, that is what you get if you try to invoke students intuition here.
Are more people going to relate more to a problem framed that way, or framed as what A has to do with B?
If you're comparing the two, it's self evident that the real world example is easier for the average person to understand. People know what price of a good is. People know that factories make goods, so there must be some supply. Demand is maybe more foreign, but I admit this domain is not the most widely understood... just off the cuff to make a point.
The solution to both problems is the same, does not require specialized domain knowledge at all, so I don't get your point.
There are plenty of more culturally widely understood domains we could use, rather than economics. Physics is of course the easy go to. Not sure what you mean by ridiculous views on physics, clarify?
Kids dont know basic physics naturally. They need to learn that and it takes quite a lot of effort.
Using physics examples kids who struggle with C = 40*B is not making it simple. It is complicating whole thing by making claims the kids don't believe yet.
Have you ever tried to argue with an average person? Those deductions aren't simple to make at all.
> Are more people going to relate more to a problem framed that way, or framed as what A has to do with B?
All students have already seen countless of examples of what A and B can be. So when they see an equation with A and B they can relate it to apples, to money, to distances, to mass, to temperature etc, at once. If you use special names for the variables most students assumes that the equation only works for those variables and either memorises it or tries hard to understand what makes those input kinds special.
Edit:
> Physics is of course the easy go to.
If you use physics then your class is no longer a math class but a physics class. It takes years for students to build intuition for even basic physics.
> Not sure what you mean by ridiculous views on physics, clarify?
Before newton people didn't understand rate of change or movement properly, instead they came up with shit explanations like this:
> Based on Aristotelian physics, Scholastic physics described things as moving according to their essential nature. Celestial objects were described as moving in circles, because perfect circular motion was considered an innate property of objects that existed in the uncorrupted realm of the celestial spheres. The theory of impetus, the ancestor to the concepts of inertia and momentum, was developed along similar lines by medieval philosophers such as John Philoponus and Jean Buridan. Motions below the lunar sphere were seen as imperfect, and thus could not be expected to exhibit consistent motion. More idealized motion in the "sublunary" realm could only be achieved through artifice, and prior to the 17th century, many did not view artificial experiments as a valid means of learning about the natural world. Physical explanations in the sublunary realm revolved around tendencies. Stones contained the element earth, and earthly objects tended to move in a straight line toward the centre of the earth (and the universe in the Aristotelian geocentric view) unless otherwise prevented from doing so.[25]
https://en.wikipedia.org/wiki/History_of_physics#Medieval_Eu...
That was what the best of humanity could come up with over 2 millennia. You can't expect an average modern high schooler to do better than that without first being taught physics.
Demand = 100 + 50*Price
Supply = 50 + 20*Price
extremely confusing! What are the units of demand? Is it units per day, average units per capita of a population? Is it in money? It surely must be money, since it is equated to Price with a unitless constant in-between. Then, do the two prices on each line refer to the same quantity? No, it cannot be, for one concerns demand (the price that people will pay?) and the other supply (the money that it costs to build something). Thus these two equations are unrelated on first sight. There must be some hidden, "obvious" relation between them but I'm at a loss. I'm not making things up, this is really what I see here. I'm a 42-year old who knows something about computers, physics and mathematics, but nothing about economy, and these two lines are utterly mystifying.Now, for this:
A = 100 + 50*C
B = 50 + 20*C
This is just two linear equations in three variables, which has a one-dimensional space of solutions.It's easier to do abstract reasoning (spotting deep connections between patterns) when you abstract things. I'm pretty sure this has some solid evidence behind it.
It's really a question of whether you want to teach solving problems in general, or teach how to reliably solve a specific problem. If it's the latter, sure, in other subjects (e.g. accounting, science) they use specific terms a lot more, because the problem is more important than the problem solving.
As a teaching tool, teachers start with "3 apples" rather than "3x" problems. This is usually closer to K than 12 though.
Not sure what you mean. Providing context does not change underlying math or mechanics of solving the problem at all. Just the same as if you asked somebody to solve FizzBuzz or BeepBoop.
What it does is make the rote exercise of solving more meaningful and relatable. Things that are relatable tend to be more easily internalized.
Talking about early childhood apples etc is missing the point. I'm talking about generic methodology to learn a new concept in a timeboxed way, not a multi-year development. Though thinking behind the two is the same.
And before you say "just learn those subjects first then?", often it is easier to first learn the abstract math and then learn those concepts than the other way around, since making sense of those equations is hard even when you do know the math and close to impossible when you don't.
Take the math for Physically Based Rendering (PBR), for example the Cook-Torrance reflectance equation.
For me at least, it's 1000x easier to understand with descriptive variable names than with L, p, w, kd, c, ks, D, F, G, n, L, dw
No idea where else this equation is useful because it used single letter variables.
Single-letter variables are extremely superior if you're working out math on paper or at a board. It is simply not possible to work through a long and complex calculation or derivation with variable names that are not compact.
You also end up concentrating more on structure than on identity. You recognize idioms (like the dot products in your example) and it almost doesn't matter what the things being dotted together are; the physical form of the problem guides you to what they must be, even if you lose track. There is only one way it can go.
The flip side is that if someone else does the derivation, and you just need to use the result, it's basically completely incomprehensible to you. You haven't put in the time to understand the problem yourself (if you had, you'd "just" have derived or at least worked through everything yourself), so the extra affordance of long, descriptive variable names often makes a tremendous difference to final understanding.
This, incidentally, is a major point of difference between programming code and mathematics. For any good mathematics problem, there is only one right answer, and any attempt to solve that problem will reach it. (Possibly in a different guise, but the solutions will certainly be isomorphic.) Programming is so often business-driven or real-world-constraint-driven that this is not true. Two attempts to solve the problem may diverge radically. And no one will ever derive business logic from ZFC set theory! So for mathematicians, the fundamental understanding of the problem domain necessary to do good mathematics enables the use of terse, fluid notation. Since programming just doesn't work that way, its verbose, rigid notation is much more useful.
A lot of people are bad at math, but decent programmers. Yet, programming is basically just composing expressions the same as you would in math? Why the disparity?
Then the more you abstract things the less variable names matter. If you create a general purpose list calling its content type "item" or "x" are both equally readable since "item" doesn't say anything that "x" doesn't.
Now math, the entire subject of math is just a bunch of abstractions. Now there are a lot of concrete applications of math, but math itself isn't concrete.
The notation did not developed because people were bored. The notation developed and sticked because it made expressions easier to deal with.
School math was hell because my brain does not memorize useless uninteresting stuff.
A student starts in some state and that state may not have a direct transition to “understanding abstraction”.
A teacher needs to understand the state the student is in and find a sequence of transitions that lead to the desired state.
It’s difficult for teachers to do this if their expertise is limited to knowing what the final state should look like, but not being familiar with (or having forgotten) the state space that leads there.
What do you do when you need more than 26 variables in your program?
Couldn't disagree more.
The whole point is that you don't care about the meaning of the numbers. They are just numbers. A big part of math is learning to strip numbers of their context and look at them bare.
Besides, variables with several letters in them are extremely ugly. They look like products. (They should be banished from programming languages also, but I realize that this is a controversial idea.)