3 ms·
I’m working on a feature that is a moderate refactoring and extending of an existing feature. I’m in some sense taking extra burden by ‘sculpting’ my change out
by tmn 2y ago
I’m working on a feature that is a moderate refactoring and extending of an existing feature. I’m in some sense taking extra burden by ‘sculpting’ my change out of the existing code and the working backwards to come up with the logically contained and discrete commits to get from where I started to where I want to go.
I would be nice to just make my change without having to show it in a series of discrete steps.
I’m not actually opposed to this standard, but trying to show one perceivable downside that op may be alluding to (I’m not actually sure?)
- deleted 2y ago[deleted]
- sethherr 2y agoThats not version control, that’s something you’ve chosen to do with version control. You could just check in your code every night. And, vs not having those commits (even without messages) - what could possibly be the downside?
- tmn 2y agoMaybe your confusion is in your assumption of what’s being discussed
- sethherr 2y agoI’m discussing version control.
- tmn 2y agoAnd everyone else is discussing behaviors that are down stream of version control
- drawfloat 2y agoBut 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.
- arthens 2y agoIf 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.
- tmn 2y agoThis is all in a professional environment requiring code review for actual submission. I need to follow this process to actually deliver
- sethherr 2y agoThis sounds like you’re discussing code review and coding standards, not version control.