[Cthulhu_]

That's what I was thinking, but then, it is very specialized and high performance code well outside of my domains (font rendering, shaders, C++, high performance / frequently called code is very much not my bread and butter). I frequently glaze over whenever trying to read a post about some optimization problem. Fast inverse square root [0] is succinct and cleanly written even though it uses math symbols instead of variable names, but I have no idea how it works and don't have the math basics to even know when / where / why to use it.

[0] https://en.wikipedia.org/wiki/Fast_inverse_square_root

[zelphirkalt]

Usually it is dangerous to let such people write application level code, but according to the reports in the comments, the guy might be one of the few exceptions, who gets the low level right, but also created flexible extensible structure of code in other places, without it becoming obscure on the application level.

Usually when I see some mathematical code that's not explained at all and has obvious flaws in terms of simple improvements that could be made to improve readability or even something as simple as some comments, I just keep thinking: "Please don't let this person touch application level code!"