I'd only clean it of stuff like passwords and such, and add a header that the code is provided as-is. You could add a disclaimer that the code was worked on un

I'd only clean it of stuff like passwords and such, and add a header that the code is provided as-is. You could add a disclaimer that the code was worked on until it provided a satisfactory result, and no further, and is not intended for (any) use. You might even add that, except for outright, actual errors that affect the result of the research, comments are discouraged. I often publish very bad code, terrible terrible spaghetti, it's not how I write code at my job, because at my job, I'm paid to produce not only working and correct code, but also code that is maintainable and understandable and follows certain practices. However, my hobby is not writing corporate code, but writing code that get done what I want to get done, nothing more, and sometimes less. It might even have actual bugs in it that I can plainly see and don't care about because they don't affect my uses If people can't tell the difference, I don't care, not my problem. If a future employer can't tell the difference, I won't work with them.