Whenever you see a lot of "Hello world!"-esque tech posts on how to do something, you can safely assume that it's 95% about building a online presence / reputation, and 5% about being helpful to the beginners.
I love good tutorials as much as the next person, but this constant CV-building nonsense is getting tiresome.
(I ran into that video while I was searching for "tips on searching for specific source code fragments on GitHub" and this title matched, and it was not what I thought it is :D)
It is an advantage for those who can afford to have side projects. Those who have other obligations, can't afford to spend time on unpaid work, or are good at the job, but not passionate about it, are at disadvantage.
For someone from a developing country, changing careers or looking for remote work, an online presence can provide them with opportunities they would not otherwise be able to get. Of course, that online presence should actually have something substantial and probably shouldn't take the form of yet another basic tutorial blog post.
Also, there's no reason why a programmer's online presence should be only about side-projects or programming. Running a website related to one of your other hobbies is a perfectly acceptable way to provide a conversation starter (which is all an online presence is doing most of the time, anyway).
It is not nonsense if you are genuinely interested in participating in those online activities (or happen to enjoy contributing to some open-source projects).
And if you do participate, you will leave an online trail that will help your potential interviewer to get to know you better (what technologies you actually know and how deeply; what your coding style is; how good you are at writing code in general; that sort of thing).
Of course, much of that can be established during an interview. But every additional data point helps to better assess the candidate.
So the point is, it’s not that they should, but it helps if they do.
Apart from just the code itself, having side projects is a good sign of valuable, non-technical skills. Such as intellectual curiosity, ability to start/finish things, and if it's a collaborative open source project, can play well / collaborate with others.
People think that somehow interviewers or hiring managers are going to dig through some random repo and assess it, but frankly there’s no time nor motivation. The most I’ve ever done is click some links, and see if the repo is just 3 files, or if it’s more substantial. There’s just not any time for anything more, and it’s all going to become clear during the interview anyway.
Why? It's substantially nonsense. Many of the best programmers I've worked with don't do, or don't showcase, side-projects. And why should they? They've got families and other interests.
Who wants to be stuck in front of a computer all the time? (He said, ironically, whilst typing a HN comment on a Sunday evening.)