But only if you choose to use them. I agree with the other commenter, it's very hard to see what trade offs there are to pressing a button to initialise a repo at the start, then committing any changes at the end of each session/intermittently so there's a copy of current progress somewhere?
If the OP is referring to version control because they're needing to handle multiple branch types, switching between versions etc that is much more involved....but also makes it even harder to see how you can manage that by simply dropping version control entirely?
From the article, it does seem like it's not about any sort of specific feature they use, but rather the sheer basic "save versions of code" aspect of VC:
"Version control kept me attached to the past"
To go back to an earlier comment, this honestly sounds like burnout to me if you're having temporal anxiety from saving code.
If it's your personal project, you are in charge of deciding which "behaviors that are down stream of version control" you want to adopt. If you are applying unnecessarily complex processes for a given project, that's on you.
