Hacker News Reader

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).

> - 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.

I think it is meant to be a joke like ZeroVer.

You change the line, and add a comment explaining what the code used to do?

This, or add another cat photo to assets

I 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.

Reply on news.ycombinator.com