Yes, I certainly thought your advice was outdated.
An astonishing amount of code in use even today was written by university students. The Linux OS - started by Linus Torvalds as a student. Students at the University of Staffordshire got to 'improve the kernel' as a side project and again, lot of their code forms the bedrock of operating systems all over the world!
Therefore 'just graduated no experience' is no excuse - perhaps your husband's degree was lacking in rigour. Or, he just did his homework and didn't explore any more. Or maybe, he didn't showcase what he'd done thinking it wasn't that important. Bill Gates, Mark Z all spent hours working on their own projects. Few know that, while he's known as a business man Bill was a very capable programmer and in fact contributed to a paper with one of his lecturers, solving an algorithm problem presented to the class. For fun.
Furthermore, 20 years ago because computer science degrees were not that common companies much preferred taking on top graduates from good universities from any degree and training them. Others were people who had done some sort of programming or been exposed to it in an unrelated job and worked their way up.
I'm not knocking your husband. My own went to a bottom ranked university more recently. But he is an excellent programmer. By the time he had graduated he had lots of personal projects on his GitHub portfolio and interviewers were falling over themselves to hire him. I worked with many people daily who went to bottom unis 20 years ago all had their passion projects.
Any 'RG', Cambridge whatever student that has only done their homework and nothing else - instant reject :)
In 2023 most interviews are automated as well people who pass the first few stages have a good chance of getting an interview - no CV sift at the first stage. And there's at least one 'degree blind' interview. I can tell how competent someone is, I don't need to see their degree to know that. In fact I'm extremely wary of hiring 'rockstars', top academically who cannot cope with imperfection and uncertainty. Because technical roles are as much about the 'least worst' solution for non-technical reasons as they are about technical competence.