3 ms·

I disagree. Version control very much impacts the process of writing code. For example, if I'm going to make a major change to a solo project but I don't know w

by nv-vn 11y ago

I disagree. Version control very much impacts the process of writing code. For example, if I'm going to make a major change to a solo project but I don't know what angle to approach it from, I'll create a branch to test one approach and another to test a different approach. If I'm unhappy, I can always branch from master again. The alternative would be to either attempt to make as few breaking changes as possible or test out exactly one at a time and lose progress when I go from one approach to another. Also, if I need to go back to an older version to fix something broken or remove a part of my code, commit messages document the changes so that I don't have to think of the code as a linear timeline of changes and search for the date, but rather search for commits that include keywords in the names and focus on those.

cturner 11y ago
You can do much of what you described by copying directories around, keeping a text file running sheet and judicious use of winmerge. The key thing is to be managing complexity. git provides good mechanisms for this but it is not the only way. Linus didn't use version control for at least a decade, either. git started out as an automation of an existing manual process he had.
- imdsm 11y ago
  > You can do much of what you described by copying directories around, keeping a text file running sheet and judicious use of winmerge. Sorry, but can I just check, are you saying this is the alternative as in you SHOULD do this, or are you saying this is the alternative as in you SHOULD NOT do this? It's just the way you wrote it sounds like you're saying this is the recommended way of developing, which I'm sure is not what you meant. Also, is winmerge available in .deb/.rpm?
  - cturner 11y ago
    Your post is passive-aggressive from start to end. If you state questions respectfully I'll have a shot at a response.
  - to3m 11y ago
    Winmerge is Windows only. I imagine this means this strategy can't be followed at all unless you use Windows? ;) The approach is an alternative, as in: you can do it. I used to work that way before I used version control, and I know I'm not the only one. I definitely prefer the workflow with version control, that's for sure, but some seem not to find it especially compelling when working alone and that is their prerogative. When you're working on your own, any process is fine, if you are comfortable with it. The object of the exercise is to create useful/interesting/etc. products for people to use/enjoy/etc. - and you'd have a hard time arguing that this is a goal Dwarf Fortress has failed to meet. (Unsurprisingly, I've yet to meet anybody that's preferred working without source control on shared code. But perhaps they do exist.)
- jmilloy 11y ago
  This is still version control, just without very many features and easy to mess up.

by nv-vn 11y ago

cturner 11y ago

You can do much of what you described by copying directories around, keeping a text file running sheet and judicious use of winmerge. The key thing is to be managing complexity. git provides good mechanisms for this but it is not the only way. Linus didn't use version control for at least a decade, either. git started out as an automation of an existing manual process he had.

imdsm 11y ago
> You can do much of what you described by copying directories around, keeping a text file running sheet and judicious use of winmerge. Sorry, but can I just check, are you saying this is the alternative as in you SHOULD do this, or are you saying this is the alternative as in you SHOULD NOT do this? It's just the way you wrote it sounds like you're saying this is the recommended way of developing, which I'm sure is not what you meant. Also, is winmerge available in .deb/.rpm?
- cturner 11y ago
  Your post is passive-aggressive from start to end. If you state questions respectfully I'll have a shot at a response.
- to3m 11y ago
  Winmerge is Windows only. I imagine this means this strategy can't be followed at all unless you use Windows? ;) The approach is an alternative, as in: you can do it. I used to work that way before I used version control, and I know I'm not the only one. I definitely prefer the workflow with version control, that's for sure, but some seem not to find it especially compelling when working alone and that is their prerogative. When you're working on your own, any process is fine, if you are comfortable with it. The object of the exercise is to create useful/interesting/etc. products for people to use/enjoy/etc. - and you'd have a hard time arguing that this is a goal Dwarf Fortress has failed to meet. (Unsurprisingly, I've yet to meet anybody that's preferred working without source control on shared code. But perhaps they do exist.)
jmilloy 11y ago
This is still version control, just without very many features and easy to mess up.