Oxidizing the Technical Interview

Reads like a novel of compilers and optimizations

It's Danish for "One more for the javanissen", which is explained later to be a little gnome that represents an anthropomorphized version of the JVM who needs an extra byte in addition to the buffer allocation lest it creates segfaults.

Is this the same author that wrote this legendary StackOverflow response?

https://stackoverflow.com/a/1732454

Same style, methinks.

I can see the influence of Aphyr's classic posts on this one, but a bit of constructive feedback:

* If you're going to emulate a writing style, you need to go all in. Study the word selection, cadence, choice of punctuation…go back regularly to ensure you're consistent with it. Once you set up a reader's expectations, anything that doesn't match will stick out and break their immersion. Read it yourself, and then if possible get others to read it too and do the same thing: hopefully they'll see the problems you may have missed.

* Each of the original blog posts had one specific "technical flex" in mind, and they stayed on topic. The one here is not quite clear: it seems like it's "programming on the bare metal", but it does too many things for a result that isn't all that surprising. Ok, you ditch Rust's standard library, and core features of the language…but then you copy paste it back anyways, and after that you link against libc and call printf. The point is to show that you can do better with all your work, not the same.

* At the very end: you are an expert Rust developer, better than your interviewer. You know you're not going to get an offer, but you didn't want one from them anyways. You're certainly not desperate to impress them.

Now that I've read the whole thing, a couple of technical comments:

* You can use -lc on macOS, libSystem will handle it for you.

* The existence of a "frame pointer" is a myth spread by bad programmers. There's no point in touching that register and certainly no need to waste two bytes stashing it on the stack, for goodness sake!

It looks like it supposed to be a Scandinavian language, most likely Norwegian or Danish. It could be interpreted as Swedish as well, in which case the correct corresponding Swedish sentence would be "och en till javanissen". A "nisse" is in Swedish something like a gnome, so "javanissen" would be "the Java gnome". The full translation would then be something like "and one for the Java gnome".

I'm not sure if there's any deeper meaning to the joke. I didn't think much of it until I read the subsequent paragraph of the text and figured out what was meant by "og én til javanissen".