Natural languages are not precise, and they lead to misunderstandings.
Re programming: Some languages are simply better at expressing certain types of programs than others, C may be great, but it gets pretty hairy when you try to use it in certain parallel/concurrent coding contexts (i.e., you're probably using a lot of extra libraries and tooling).
Re music: Could you imagine expressing any piece of significant length or complexity in plain English? Even a mathematical (concise and precise) symbolic language would prove difficult, compared to the visual and multi-dimensional notation customarily used. (At least for reading, a case could possibly be made for more expressive and concise notations for writing musical pieces.)
Re natural languages: This is why we borrow so many words in English (and other languages, I'm sure) from elsewhere. A larger set of words allows us to produce more expressive and nuanced statements and questions.
It's still math.
What is the square which when taken with ten of its roots will give a sum of thirty nine? Now the roots in the problem before us are ten. Therefore take five, which multiplied by itself gives twenty five, and amount you add to thirty nine to give sixty four. Having taken the square root of this which is eight, subtract from this half the roots, five leaving three. The number three represents one root of this square, which itself, of course, is nine. Nine therefore gives the square.
He's solving x^2+10x = 39 by completing the square.
n >> k >> ln(n) >> 1,
he says "Specifically, we require n much greater than k much greater than log n much greater than one", and says it's unwieldy. Well, if you say it like that, then it is.
"Specifically, we require than the magnitudes of n, k, log n, and one be in decreasing order with significant distance between each."
Not a problem. Just don't try to read notation literally in the order it's written.