3 ms·
I find git commit hash too long for no good reason. I prefer to version with the file size, which is strictly increasing if you follow those best practices: -
by GerryLefaux 5y ago
I find git commit hash too long for no good reason.
I prefer to version with the file size, which is strictly increasing if you follow those best practices:
- never delete any of your valuable code (commenting out is OK)
- never break up code into several files (makes it simpler to read).
- ModernMech 5y ago> - never delete any of your valuable code (commenting out is OK) So how does this work if you want to change a line in a function? Do you just comment out the line and write a new version below it? i.e. if I want to fix a bug in my code, I can't just fix it, I have to add a line of code to my program. How does this system work in practice? The way I code, it seems like this would lead to a huge file that is mostly commented.
- maple3142 5y agoI think it is meant to be a joke like ZeroVer.
- Scarblac 5y agoYou change the line, and add a comment explaining what the code used to do?
- quickthrower2 5y agoThis, or add another cat photo to assets
- da_big_ghey 5y agoI hope you are making a joke, if not, you will be overjoyed when you find a source control system and can tidy your source file.