I just hope the leetcode and other dubious interviewing techniques goes away with it as well
Second best is a GitHub repo but often those I have seen simply included test apps resulting from a CS course or perhaps worse, code copied from somewhere else.
Regardless, app or code (or both) give the interviewer something else to talk about with the candidate about (and you would expect a good deal of enthusiasm from the candidate in this kind of discussion).
* Nobody asked culture-fit questions
* Nobody was interested in portfolio, side projects, or GitHub.
* I was not asked questions related to the role.
* Only presented with a leetcode screen
If you move away from the FAANG/unicorn scene, the interview process becomes more personable, and I was actually asked questions related to the role.
The premise of emphasizing leetcode is to get developers who can solve problems fast.
But if the only thing someone knows is competitive programming, and not operating systems, distributed systems, network protocols, serialization formats, libraries and frameworks and pretty much everything that's required to implement actual software, that person won't be able to solve problems fast. In fact, that person may reinvent the square wheel and waste resources.
The only reason I have any open source work on GitHub now - I stopped programming as a hobby the minute I graduated from college in 1996 - is because my company has a very straightforward open source process where I can open source reusable project work I do for customers (consulting).