I haven't tried to decipher this, but I believe it is a case of the following:

When you call a function in C, the compiler will convert this into machine code which points the instruction pointer to a specific address in the memory (after setting some values on the stack as arguments, say, or in special registers depending on the architecture conventions). The compilation process will also turn the function instructions into binary code and this code will be placed at aforementioned memory address, so that the required function code runs once the instruction pointer is pointed there.

Here he has looked up the binary needed for the function, and converted it into text via ascii lookup (or used an assembler ect.). So the binary that the compiler thinks is text actually gets run as a function. If you learn some assembly this isn't too hard to do, in fact you can practise NASM on this site, and then look up the opcodes etc.

Approved by someone