Sure, if you don't want people to look at your code, don't make it public?
I'd argue with you that a GitHub profile could be a useful signal, but it's not a given.
As a hiring manager:
- If they don't have a GH profile, I won't ding them.
- If they add it to the resume, and it's a scrap yard, I won't ding them.
- If they add it to the resume, and it's well maintained, I will ask questions about it.
- If they add it to the resume, and it's clearly deception, I will have a negative perception.
I feel like most hiring managers take this approach.
Your comment is a great reason for me not to share my Github profile.
I'm not going to treat my Github project defensively. The notion that most people need to worry about what they put in their README because some interviewer is going to look at it - it's just so much better not to let them see your Github profile.
The irony with this article is that it's proposing a solution to a problem - yet that solution is as problematic. A resume is a poor indicator of one's skills, as is their Github profile.