10 ms·
Oxidizing the Technical Interview
- steve76 6y agoSomeone with a lot more going on asked you a question, and you took 20 minutes to write "InstallGentoo!" Under that metric, the position went to someone who submitted a fabrication design for a MOSFET. Want different input? Just put in another work order at the plant. Sure you're smart. No one wants to work with you, just like mules are the toughest animal but no one wants them around because they foam sweat all over you. I'm just thinking what it would be like working next to someone like this for the next 20 years. Day one, you're already a problem. High nail gets the hammer.
- rvz 6y agoNice 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 an 'optimal solution', just don't tell candidates to do this on a whiteboard in >20 mins. You might as well ask for a candidate to do it in LLVM IR. EDIT: Even though the whole post is a great hack and a joke as I already outlined earlier, it still looks like some HNers still can't take/see jokes! %:O)
- empath75 6y agoI think that’s obvious no? It clearly says at the end that he didn’t get the (imaginary) job.
- ChristianBundy 6y agoThat's the joke. :~)
- ascendantlogic 6y agoYou did the super double meta joke and everyone missed it.
- flak48 6y agohttps://en.wikipedia.org/wiki/Poe%27s_law https://en.wikipedia.org/wiki/Poe%27s_law
- troughway 6y agoAlternative title: Rust for C++ Template Lords.
- gumby 6y agoEven back in 90s people circulated jocular constant time factorization programs in C++...nowadays they'd be even easier to write.
- ZeroCool2u 6y agoI 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-interview https://aphyr.com/posts/340-reversing-the-technical-intervie...
- iamrecursion 6y agoIt says this at the top!
- ZeroCool2u 6y agoYou're right! I didn't realize until you pointed it out.
- throwaway_pdp09 6y agoTo each their own, but it's offputting for me. I like it short and pointed.
- kixiQu 6y agoLuckily, there's a lot of that kind of content out there already.
- d3nj4l 6y agoThe best of aphyr's series is Hexing the technical interview (https://aphyr.com/posts/341-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!”
- dvtrn 6y agoif Upton Sinclair was a SWE who also wrote short stories I like to think many of them would read a lot like this. Beautiful. Bravo. More please, I enjoyed this too much
- mgattozzi 6y agoI'm glad it brought a smile to your Friday :D
- riazrizvi 6y agoThis is how I imagine it feels to code on bootleg Adderall. It gives you the power to deliver a comically useless end product, wrapped in such a fantastically prolific technical show that most people fall for it.
- flmlta 6y ago>bootleg Adderall You mean meth?
- vertex-four 6y agoNo, amphetamine is significantly different from methamphetamine.
- riazrizvi 6y agoMethamphetamine, was developed by the Nazis after seeing how effective the amphetamine Benzedrine was for the American team in the '36 Olympics. Under the name Pervitin, the Nazis used the drug throughout WWII, it enabled them to keep fighting for days on end. Blitzkrieg was partly a byproduct of meth. This is also part of the reason why German troops found it so easy to murder large numbers of unarmed people during Barbarossa in the name of heartless Nazi ideology - meth-heads lack empathy. See Killer High by Peter Andreas for more fun military history about drugs.
- vertex-four 6y agoI don't know much about that, but I do know that methamphetamine is a significantly more grim drug, being neurotoxic in moderate doses - I've used a few stimulants but I wouldn't touch that.
- mjburgess 6y agoIt reminds me of the interviews I used to do at c. 18 -- at first, the framework must be defined, and then the solution to the problem. The framework comes ab initio, because i'd spend my teenage years hysterically refining versions upon versions of them. I might well do the same thing now. It's a seductive display of sheer hubris.
- kkcorps 6y agoThis article just gets better with every line.
- zozbot234 6y agoThis 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.
- pietroalbini 6y agoThat flag shouldn't be documented: it's completly unsupported and meant to be used only by the compiler. Please don't rely on it :)
- mgattozzi 6y agoYeah I included it only as part of a joke and no one should actually use it because it completely subverts stability and if someone put this in a build script to set that env var it would be very very bad
- estebank 6y agoTo expand on it, there's no assurances of that flag working, and crates relying on it to work on stable are breaking all compatibility guarantees the language restricts itself to. Updating stable compilers can break your crate, and nightly features in stable and beta do not receive backports and them being broken won't stop a stable release, so it's pretty much like running on nightly unless you know what you're doing and take on the responsibility of maintaining the stability assurances yourself. That being said, it can be useful in closed source repos for specific circumstances. It would be nice if we changed what the flag is named every stable release as a way to "discourage" its use. I wonder if I should write an RFC.
- yellowapple 6y agoIf it exists, then it should be documented. If it shouldn't be documented, then it shouldn't exist.
- draw_down 6y ago> They're a younger engineer and you are being tested for a Principal Engineering position Found your problem!
- umaar 6y agoI like this style of writing, feels like storytelling, rather than something purely instructional. As someone who doesn't do Rust, the code lost me a little, however it has been one of the most loved technologies on the Stack Overflow Developer Survey [1] and that has me intrigued. On the subject of technical interviews, I recently collected, cleaned up and published [2] the code exercises I submitted to Monzo, Geckoboard, SitePen & Masabi (and a Google one which I didn't actually submit). All code solutions, except one, let me proceed to the next stage of the application process, and I hope this can help others, or at least offer an interesting insight. [1]: https://insights.stackoverflow.com/survey/2020#most-loved-dreaded-and-wanted https://insights.stackoverflow.com/survey/2020#most-loved-dr... [2]: https://umaar.com/blog/my-code-exercise-submissions-part-1/ https://umaar.com/blog/my-code-exercise-submissions-part-1/
- lucasgonze 6y agoThis article is clearly invalid because attempting to email Z̴̧̡̢̨̛A̷̡̡̢̢̡L̶̢̧̢̪̬Ģ̵̡̢̢̧̛Ơ̵̡̡̬͇̬ ̵̡̧̢̛̳Ċ̷̢̨̢̼̰Ǫ̷̨̧̢̛͎M̵̡̨̖̹̣E̴̢̧̨̨̛S̸̱̠̹̮̣@gmail.com using Gmail produces this error: Error The address "Z̴̧̡̢̨̛A̷̡̡̢̢̡L̶̢̧̢̪̬Ģ̵̡̢̢̧̛Ơ̵̡̡̬͇̬ ̵̡̧̢̛̳Ċ̷̢̨̢̼̰Ǫ̷̨̧̢̛͎M̵̡̨̖̹̣E̴̢̧̨̨̛S̸̱̠̹̮̣@gmail.com" in the "To" field was not recognized. Please make sure that all addresses are properly formed.
- sp332 6y agoI haven't found a punycode encoder that can gracefully handle an input this long, but it should be possible to make an equivalent gmail address with about 124 ACSII characters.
- sp332 6y agoI guess the problem was that the local part has a space. Let's replace it with an underscore and we get: zal_mes-55a8ss0clxz2ivbded0gccaaccafieacacagabf9af3jlfjijxcffa5e8eja5kzd9c8fxb5agq5a0d1af8fvcm5pm4a6p@gmail.com Which is 111 chars. If it allowed spaces in quotes, which is RFC-compliant: "zal mes"-4eb6x27ct1aw3j5bdccd5hecaaccabfkeacacagcabf4bf0llfggil1acffa3fyfja1m8dtd5e4a4c7agfq7a8d7af6g1cm9rm6anr@gmail.com 122 chars.
- m3kw9 6y agoReads like a novel of compilers and optimizations
- pmcollins 6y agoIs this the same author that wrote this legendary StackOverflow response? https://stackoverflow.com/a/1732454 https://stackoverflow.com/a/1732454 Same style, methinks.
- mgattozzi 6y agoNo I'm not, but I did reference it.
- boromi 6y agoI really like the blog style. Any tips on how I could setup something with a smilar theme.
- saagarjha 6y agoIt's the default Ghost theme, I think.
- saagarjha 6y agoI 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!
- fasterthanlime 6y agoIt seems you're trying to emulate one of Linus's classic rants with that comment, but if you wouldn't mind a bit of constructive feedback: * The word selection in your comment isn't quite right. Linus has been known to use expletives others deem inappropriate when reviewing another human being's work - but since that's what you seem to be going for, you might as well commit to the bit. * The big difference between your comment and Linus's rants is that he's doing it when giving feedback that other people actually requested, rather than going off at some random person on the internet. * It seems your Linus impression is also a bit out-of-date, as he has publicly apologized for being a jerk in 2018. Maybe you were going for "vintage Linus", but it just didn't cut it for me. Although you've nailed the attitude there, I fear the real problem in your comment writing is that it's not backed by a solid knowledge of what you're writing about. For example, it seems you wrote 80% of your comment before reading the entire article? This may be a throwback to other classic comments I'm missing - but if I missed it, then others will too, so it seems the onus is on you there. Now that I'm done reading your whole comment, I must say I wasn't very surprised, but also not very impressed. I've read better comments than this one before, and I couldn't really tell what you were trying to achieve with it. Next time try adding a table of contents, maybe some primary sources, or consider not attempting that kind of comment at all, if you're not confident you can pull it off? Just my two cents!
- nice_byte 6y agousing system printf instead of programming with ioctls? weak.
- peter_d_sherman 6y ago>"You look back upon those years fondly as it's turned you into the programmer you are today. An unparalleled Abyss Gazer, an Eldritch One, one who makes mortal men fear and worship the code you've wrought upon this world that holds the very foundations of it together..." That is some great writing; some great prose! Perhaps in another life, one where they didn't have computers -- you would have considered becoming a Writer? Like if you wrote a SciFi novel... I (and probably a lot of other people!) would read it!
- gerbilly 6y agoOoh, this article lost me at the first sentence. (young'in, really?) Sadly for me, whatever wisdom it may have contained will have to remain a mystery.
- yellowapple 6y agoSure is amazin' that y'all would write off a whole doggone article on one teensy weensy colloquialism of the 'merican workin' class, I reckon.
- gerbilly 6y agoI said the article lost me at the first sentence. It doesn't mean I stopped reading there. I still gave it a chance and read the next few paragraphs before finally giving up on it. I don't mind colloquialisms where they add to the depth of the content. The article in question, however, is written in a circumlocutory style that suggests more effort was put into the style than the substance. I admit that it's possible that the signal to noise ratio in the article is better than I assumed, but I don't have to subject myself to tedious writing when there is so much good stuff I could be reading instead.
- yellowapple 6y agoIt's telling a (what I assume to be) fictional story. It doesn't need to be some dry technical article just because it happens to have some Rust code in it. Like, if that ain't your thing, then so be it, but I think you're assigning values to it that simply don't apply. That is: if you were reading a novel or short story, would you have the same complaint?
- gerbilly 6y agoYes I would have the same complaint about the writing style.
- yellowapple 6y ago
- 2OEH8eoCRo0 6y ago>You look back upon those years fondly as it's turned you into the programmer you are today. An unparalleled Abyss Gazer, an Eldritch One, one who makes mortal men fear and worship the code you've wrought upon this world that holds the very foundations of it together. Why do people always talk about coding like this? I don't hear architects or electrical engineers talking like this.
- karatestomp 6y agoI think it's the nearness of thought to end product. If architects could actually cause buildings to appear in real life as they drafted, they might do the same thing. That plus the association with math, probably, and everyone who's into that seemingly harboring semi-mystical ideas about it ever since humanity invented abstract mathematics.
- 2OEH8eoCRo0 6y agoI was talking about the arrogance of software engineers when they describe what they do. Look at me the smartest smart guy doing things that scare "mere mortals". Give me a break and get over yourself.
- karatestomp 6y agoAh, I misunderstood. Yeah, that's silly and I think it's usually a bit tongue-in-cheek or playful. When it's not it's very, very lame. In the Lisp world I associate it with SICP, which I read as falling in the former category. Lispers (and associates) who write after that style are doing so in imitation of that, I suppose, or of some prior work that it also cribbed from that I'm not aware of.