There is bad code in everyone's repo. Several of my repos are from courses in grad school. From a software engineering standpoint, they are horrendous. But, they solved the problem the professor assigned and taught me what the professor intended by the assignment.
It's probably more helpful, in evaluating a developer, to see a progression of thought rather than shiny, functioning code.
Re:What I Learnt From Reviewing 22 CVs
by willcipriano on Tuesday July 07, 2020 @10:30AM
(#23759634)
In my experience personal projects get reviewed so infrequently that I'm not all that worried about someone digging down and evaluating the code quality of a 4+ year old repo.
Pay me 300,000$ a month and we could talk about it without commitments from my side. Otherwise I don't want to justify myself towards my employer if I work on private stuff or not. Especially not with contracts in tech, which are already borderline abusive.
That said, I haven't touched my public repositories for quite a while. Why? I have a fucking job! Aside from that I also host gitea on my domain that you will also not get to know. Maybe I would create another one for public display, but that is very unlikely.
I get that some people are forward with this stuff and in general social media presence, but I am certainly not.
edit: Of course there is also bad code in my repos, but that is completely besides the point.