The comments in this article are embarrassing. It shows none of you have even basic reading comprehension. Either you didn't read the article at all or not very

The comments in this article are embarrassing. It shows none of you have even basic reading comprehension. Either you didn't read the article at all or not very carefully: "So, instead, we have an hour-long technical discussion where I ask them questions about web vitals, accessibility, the browser wars, and other similar topics about the web. One of the questions I always like to ask is..." It's ONE of the questions, so those concluding it's a terrible interview altogether are dramatizing. As for the question being relevant or not, I think it actually does say a lot about a developer. Just those few lines of code show historic knowledge, internationalization, SEO and social networks, mobile optimization, CSS normalization, and bleeding edge features (origin-trial). In that sense it's an effective question. You learn a lot about someone with little code, even if the understanding of some individual lines is not a showstopper. Finally, saying that your framework usually generates this for you isn't the great answer you think it is.