Live data from Hacker News

Oxidizing the Technical Interview

blog.mgattozzi.dev

11–20 of 76 posts

Re: Oxidizing the Technical Interview

#11

I personally enjoy this writing style a great deal. I believe it's likely inspired by the very popular series by Kyle Kingsbury (Aphyr)[1] [1]: https://aphyr.com/posts/340-reversing-the-technical-intervie...

The best of aphyr's series is Hexing the technical interview (https://aphyr.com/posts/341-hexing-the-technical-interview), which includes one of my favourite lines from any post ever:

> “Og én,” you recite, sing-song, “Til javanissen!”

Re: Oxidizing the Technical Interview

#12
post #5

Nice jokes and great hacks aside however, unless you're interviewing for a compiler engineer position, That is absolutely overkill for this type of question to the point of unreadability. One can argue that the 'question' is too generic for this systems/compiler developer position. I would just ask you about basic LLVM internals instead. To those 'serious' interviewers with 10x developer syndrome looking at this as a…

That's the joke. :~)

Re: Oxidizing the Technical Interview

#14
post #5

Nice jokes and great hacks aside however, unless you're interviewing for a compiler engineer position, That is absolutely overkill for this type of question to the point of unreadability. One can argue that the 'question' is too generic for this systems/compiler developer position. I would just ask you about basic LLVM internals instead. To those 'serious' interviewers with 10x developer syndrome looking at this as a…

I think that’s obvious no? It clearly says at the end that he didn’t get the (imaginary) job.

That's why I said it was a nice joke and a good hack in the first place. Unfortunately, there are those few who still 'take it literally'.

Re: Oxidizing the Technical Interview

#17
post #14

Earlier quoted context omitted.

I think that’s obvious no? It clearly says at the end that he didn’t get the (imaginary) job.

That's why I said it was a nice joke and a good hack in the first place. Unfortunately, there are those few who still 'take it literally'.

There but for the grace of Linus goes my compiler.

Re: Oxidizing the Technical Interview

#18
post #5

Nice jokes and great hacks aside however, unless you're interviewing for a compiler engineer position, That is absolutely overkill for this type of question to the point of unreadability. One can argue that the 'question' is too generic for this systems/compiler developer position. I would just ask you about basic LLVM internals instead. To those 'serious' interviewers with 10x developer syndrome looking at this as a…

That's the joke. :~)

I think my comment has already acknowledged that.

Re: Oxidizing the Technical Interview

#20

This whole blog post should just be added as an appendix to the Rustonomicon , in order to provide official documentation for the RUSTC_BOOTSTRAP=1 flag.

That flag shouldn't be documented: it's completly unsupported and meant to be used only by the compiler. Please don't rely on it :)
Post reply on HN