Good morning, everyone. Fine day here, hopefully there too.
I remember a discussion on version saves perhaps a year ago. My problem is I tend to write code, save a version, run the code and if it works I keep it, if I have a serious problem I revert back to the previous version. The problem is I am building a library of versions, most of them now of little value. Problem is I can start getting lost in versions with close numbers.
Would anyone be able to reference that discussion, suggest a new discussion or offer some needed advice.
I case I do not respond after a reply, thank you very much for your help.
It sounds like you would benefit from using a version control system like Git.
2 Likes
This is what I do. My version system is Major.Minor.Bug, with the typical, albeit subjective, meanings. Every deployed change gets a new version number, and every significant change is logged in my notes. Every new version represents a bug fix or an improvement, and with more than a dozen apps in daily use by myself, my clients, and their facilities, I’ve rarely had to revert to a previous version, and then only briefly while I find the regression.
I’ve never felt the need for a formal version control system, despite the exhortations of some forum members that one absolutely must go that route. The only thing I miss out on is the ability to search across text source files, but the organizational simplicity of the binary format balances that out.
1 Like