Comment

Comment by clwk

This reads as an extended justification for how the author could possibly have failed. He writes as though it must be as simple as 'just should have asked a question'. It's an odd conclusion which communicates its own set of assumptions. It reminds me of people who claim, in all seriousness, that they can always spot X intangible characteristic — without any justification for how they determine their false positive/negative rate in that judgment. This undoubtedly reflects my bias, but I find many (bordering or even definitely including most) 'humble' blog posts to do this; and that is perhaps a further riff on the kind of canned advice we see here. They tend to read, to me, like answers to the interview questions, "Tell me about a time you failed," or, "What is your greatest weakness?" In this case, all the author really reports is that he did extremely poorly relative to his expectations — but he manages to spin it into a maxim. If even someone as qualified as he could be unseated by this tactical error, it surely bears memorializing as advice worth living by.
parent clwk 6 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton