Live data from Hacker News

Oxidizing the Technical Interview

blog.mgattozzi.dev

71–76 of 76 posts

Re: Oxidizing the Technical Interview

#71

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 :)

If it exists, then it should be documented.

If it shouldn't be documented, then it shouldn't exist.

Re: Oxidizing the Technical Interview

#72

Ooh, 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.

Sure is amazin' that y'all would write off a whole doggone article on one teensy weensy colloquialism of the 'merican workin' class, I reckon.

I 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.

Re: Oxidizing the Technical Interview

#73
Someone 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.

Re: Oxidizing the Technical Interview

#74

Earlier quoted context omitted.

Sure is amazin' that y'all would write off a whole doggone article on one teensy weensy colloquialism of the 'merican workin' class, I reckon.

I 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…

It'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?

Re: Oxidizing the Technical Interview

#75

Earlier quoted context omitted.

I 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…

It'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?

Yes I would have the same complaint about the writing style.

Re: Oxidizing the Technical Interview

#76

Earlier quoted context omitted.

It'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?

Yes I would have the same complaint about the writing style.

How boring and bland. I mean, whatever floats your boat, but that complaint would apply to a significant majority (if not entirety) of well-renowned English literature. I have enough trouble sitting through a book as-is (I'm a slow reader, since I like to "hear" the narration and dialogue in my head); can't imagine how soul-sucking it'd be to sit through a book that just told everything matter-of-factly with no narration personality whatsoever.

Like, the style's kinda the whole point. It's a key part of the artistic value of literature, and what makes literature entertaining (or at least moreso than reading a dictionary front to back).

Post reply on HN