[twolf910616]

How do you know you're not the midwit? To me it seems quite reasonable that author is the one over complicating everything, and in reality coding interviews are just not that bad.

[edit: they're not that bad in the sense that hiring is a inherently lossy process of projecting something incredibly complicated, like skills, personality, motivation, and situation into a 45 minute interview where only 1 or 2 dimension can be measured. If you increase the time/cost and do hire fast fire fast, then fine, you can get a better interview process, but it's not free. Other industries use stamps and certs to do that sorting, also not cost free. Coding interviews, yes we all hate it, but it's all a tradeoff.]

[grivant]

The author to me is pointing out that coding interviews are random and arbitrary, specially when done by junior engineers or engineers trying to protect their jobs. I’ve seen too many times coding interview given to the junior most engineer on the panel, specially at FAANG adjacent companies since they don’t know how to calibrate coding interviews correctly.

[willcipriano]

> How do you know you're not the midwit?

"Beware of false prophets, who come to you in sheep’s clothing, but inwardly they are ravenous wolves. You will know them by their fruits. Do men gather grapes from thornbushes or figs from thistles? Even so, every good tree bears good fruit, but a bad tree bears bad fruit. A good tree cannot bear bad fruit, nor can a bad tree bear good fruit. Every tree that does not bear good fruit is cut down and thrown into the fire. Therefore by their fruits you will know them."

[janalsncm]

Good trees do bear bad fruits. It happens all the time. Apparently Matthew had never been to an orchard.

[dennis_jeeves2]

>How do you know you're not the midwit?

You don't, that the point.