Hacker News Reader

Given this disclaimer at the top of every article, that sounds a bit inappropriate:

> Disclaimer: Just like most other posts on this blog, you don’t actually need to know any of that to be productive with React. This post is for those who like to see what’s behind the curtain. Completely optional!

I only want my team to be composed of those who like to see what's behind the curtain.

Everyone knows the best teams are homogeneous, and everyone knows that if a candidate hasn't looked behind the curtain of React, then they probably don't look behind the curtains of anything.

There's dozens of layers of curtains, and nobody has this level of expertise at all of them.

Have you read and understood all of tcp.c? Can we quiz you on the USB protocol?

This is from the second post:

> Just like in my previous post, you don’t need to know this to be productive in React. I didn’t know this for years. Please don’t turn this into an interview question. In fact, this post is more about JavaScript than it is about React.

https://overreacted.io/how-does-react-tell-a-class-from-a-fu...

Wouldn't you just be testing if they read the blog posts?