Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
If you have at least a few good projects, or can make some, I see little problem with several older not quite so good.
It proves you have been experimenting a lot and the good ones proves that you have learned and improved.
But maybe not every one.
I would choose those that either at least works reasonably well or show an effort of trying different things.
Most of the ones I have public are not finished and code quality is a bit varied.
My friend said I should make some of my old dead projects public (after removing passwords or api keys) even if they were badly done at least to show growth and development to recruiters.
I don't know though, I had a ton of random projects most I didn't bother with good practices assuming I'd be the only person to see the code, or telling myself I'd fix it later though eventually letting the project die for various reasons
should I really make bad projects public or should I keep them private waiting for a slim possibility of me reviving them.
question