Although I would not subscribe to the idea that VC as a solo developer is always a waste of time, there are definitely small scope projects where I do not use i

Although I would not subscribe to the idea that VC as a solo developer is always a waste of time, there are definitely small scope projects where I do not use it. If you know your project is for sure _personal_ (i.e. not shared) and a small _proof-of-concept_ (i.e. if you go further in that direction you will do a rewrite anyway), I think it is overkill. Your code and data will be in so much flux, that good old copying is faster than dealing with the VC. Thinking about it, I think it makes sense to add VC to a project, when it delivers its first satisfying result, I would call that the proof-of-concept program. At that point you throw it away/archive it, or you have bigger plans, then you probably add version control knowing you have this working prototype and rewriting stuff. You do not have the history to that point, but it would not be helpful anyway.