Code quality is overrated in a side project. As developers we love to inflate this fantasy that someone else is actually judging our line-to-line code.
Unless you're incompetent and making glaring mistakes, someone reviewing your code would have to credentialize in your codebase to identify things like bad architecture. Nobody is doing that.
I'd put your energy into polishing a quality README. That's actually something that someone else will see, and I'd assert that it's the most important part of a project for someone flipping through.
In fact, in the hiring position, when I see someone with projects but not a single README, I have to wonder if it's a bad signal. Sure, they could do the easy part of slapping code against the wall, but they stopped before the hard part of documenting/introducing it. Something to think about when you're competing with other applicants for a job.
Unless you're incompetent and making glaring mistakes, someone reviewing your code would have to credentialize in your codebase to identify things like bad architecture. Nobody is doing that.
I'd put your energy into polishing a quality README. That's actually something that someone else will see, and I'd assert that it's the most important part of a project for someone flipping through.
In fact, in the hiring position, when I see someone with projects but not a single README, I have to wonder if it's a bad signal. Sure, they could do the easy part of slapping code against the wall, but they stopped before the hard part of documenting/introducing it. Something to think about when you're competing with other applicants for a job.