Dave Rolsky, a software developer, writes about Perl, Rust, Go, security issues in libraries, and tech job hunting and interviewing.
HN links it for his posts on TAP parsing problems, Perl IP address security bugs, and interview practice. One commenter calls his interviewing style sensible.
https://blog.urth.org/2022/04/19/software-job-search-2022-retrospective-coding-challenges/#what-about-existing-projects
I have a two word answer: Intellectual Property. Not everyone is an accomplished Open Source publisher, nor should that be a requirement for employment. So what existing project do those candidates point the interviewer at? Someone else's IP? And then the hiring company is obligated in self-defense to make sure that it's not someone else's IP, lest it end up in someone's hard disk accidentally and get discovered in some otherwise unrelated audit? No. Thank. You. Keep your own code to yourself.
Now, you might point out your own code with some URLs and they may take a look at it. But that's not the same as making it part of the interview process.
TAP is better than some things, but it has some serious issues that I wrote about on my blog a while back - https://blog.urth.org/2017/01/21/tap-is-great-except-when-its-not/
Basically it's nearly impossible to fully parse it correctly.
And as predicted, the issue is turning up in other places, for instance https://blog.urth.org/2021/03/29/security-issues-in-perl-ip-address-distros/ (comments https://news.ycombinator.com/item?id=26628827)
And the above poster would seem to have an eminently sensible interviewing style, himself:
http://blog.urth.org/2016/03/08/tech-interviewer-theory/