[kstenerud]

A recruiter will take whatever you've posted publicly, and draw conclusions based on what you've presented. Whether you agree with it or not, that's precisely what will happen, even if they try not to.

It's on you to communicate your intent for things you release publicly. That means a README.md which explains what the reader is looking at. If it's just some half baked idea you've been kicking around, say so. Tell your reader what to expect, because if you don't, they WILL expect the wrong thing.

Effective communication is the foundation of any relationship, including work relationships. Show that you can communicate your thoughts. Guide your reader. Make it dead simple for them to see the best of you.

Beyond that, it's helpful to have a showcase "portfolio" project that is written as if you were presenting a finished product to a customer, including documentation, unit tests, ci, good design, the works. Showing that you can see a product through from initial design to release will impress people. Do you need it? No, but it will set you apart from the crowd.