Ask HN: Publish old projects even though the source code embarrasses you by now?

I made the games available for free on Steam because I thought they might still find some players who enjoy them, even if they are of course a bit old-fashioned here and there.

I'm now thinking about releasing the source code as open source. I'd really like to do that, because I think it might be interesting for some people. And if people create new ports or mods/improvements, that would be pretty awesome.

However, from today's perspective, the source code is not very well structured - so it's a bit embarrassing. I'm torn on whether to publish it or not, because it might reflect badly on me as a developer. How would you handle that?

But I wonder if putting embarrassing things in github would hurt future job searches ? I very much doubt that since the people doing the hiring will not have any idea what they are looking at :)

You don't want to work with someone who would think badly of you for some more than a decade old projects

No one will judge you by 15 year old code if you have recently produced good code. That's what people will look at.

Just look at the face palms at Nintendo HQ despite the amazing game they made https://m.youtube.com/watch?v=t_rzYnXEQlE

The right way to make Android apps has changed completely, and the documentation and tutorials are good now.