Is this the same author that wrote this legendary StackOverflow response? https://stackoverflow.com/a/1732454 Same style, methinks.
Oxidizing the Technical Interview
41–50 of 76 posts
Re: Oxidizing the Technical Interview
#42Re: Oxidizing the Technical Interview
#43I 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…
* 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!
Re: Oxidizing the Technical Interview
#44I 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…
It 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 yo…
Re: Oxidizing the Technical Interview
#45This 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.
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.
Re: Oxidizing the Technical Interview
#46Earlier quoted context omitted.
It 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 yo…
It seems like you're trying to be snarky, but you just come off as both passive aggressive and incorrect.
Re: Oxidizing the Technical Interview
#47I 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…
It 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 yo…
If I were, I'd probably be courteous enough to link to it as the original author did.
> 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.
I don't swear online :)
> 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.
Sadly, I tend to do this far too often, and my goal is that it is not characterized as "going off at" people. I'm working on it.
> It seems your Linus impression is also a bit out-of-date, as he has publicly apologized for being a jerk in 2018.
See above. My audience is much smaller than Linus's, so it's likely that you may not have seen my apology for being a jerk in 2018.
> 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.
Actually, I happen to have already read the linked material, so I think I have a fairly decent background in Aphyr's writing.
> For example, it seems you wrote 80% of your comment before reading the entire article?
That is correct. You'll notice that I commented on the article's style early for reasons I explained in the comment itself: I didn't need to finish it to provide that feedback, and the thing I referenced itself gave me reason to pause reading. I withheld technical feedback until I finished.
> I've read better comments than this one before
I should hope so!
> I couldn't really tell what you were trying to achieve with it.
Provide constructive feedback to the author.
> consider not attempting that kind of comment at all, if you're not confident you can pull it off
Thanks, but I personally prefer to not shut down people who are trying to improve their writing.
Re: Oxidizing the Technical Interview
#48Earlier quoted context omitted.
>bootleg Adderall You mean meth?
No, amphetamine is significantly different from methamphetamine.
See Killer High by Peter Andreas for more fun military history about drugs.
Re: Oxidizing the Technical Interview
#49Earlier quoted context omitted.
It seems like you're trying to be snarky, but you just come off as both passive aggressive and incorrect.
I'm confused - people usually love it when I give them unsolicited and lengthy reviews of their work, framed in a way they didn't intend it to be, but that lets me roleplay as someone who has authority on the matter and is talking down to them?
Personally, if someone consumed something I worked on, actively felt that there was something they felt could be improved, and didn't mention it to me, I would have felt as if they had done me a great disservice. I don't have to agree or even take their input into account, but I would very much like it to exist.
Re: Oxidizing the Technical Interview
#50Earlier quoted context omitted.
It seems like you're trying to be snarky, but you just come off as both passive aggressive and incorrect.
I'm confused - people usually love it when I give them unsolicited and lengthy reviews of their work, framed in a way they didn't intend it to be, but that lets me roleplay as someone who has authority on the matter and is talking down to them?