[blueblob]

I am currently a graduate student and I can say that I, without a doubt, worry about the quality of my code. I worry about this because I have to rely on other student-written code that often does not perform as advertised. I refactor both my code, and code written by other students very frequently even though the code is really only "proof of concept" because I need to refactor other people's code to get mine to work. I cannot stress enough how important it is to refactor (and document) code.

[xackpot]

Working across teams and developers is one more reason to worry about the quality of the code. Sometimes the code written in not as per our vision and we end up refactoring it. But again, all these things are possible if there is some time at hand. For startup like ours, we are continually iterating and adding code proof points. This makes it difficult to maintain the quality of the code how much ever we want to. I like your idea of documenting, though again, it's time consuming. We do it with helpful comments, but I think it is not enough.