3 ms·
You code differently using Git vs SVN? That's an interesting concept. It doesn't change the way you code it just changes the way we share code.
by Thaxll 10y ago
You code differently using Git vs SVN? That's an interesting concept.
It doesn't change the way you code it just changes the way we share code.
- gowld 10y agoIt doesn't change how I code. It changes how we code.
- jasonwatkinspdx 10y agoGit makes multi-tasking on multiple branches far easier than SVN. In the SVN days I always had multiple checkouts and a pile of scripts for changing/updating to branches for handling a few regular tasks in that context. Once git won I was able to delete them and have a far simpler workflow.
- nstj 10y agoGit absolutely changes the way I code. Cheap feature branching and easy rapid collaboration are huge in how they influence my coding practice and output. I wouldn't enjoy coding anywhere near as much if it weren't for Git.
- VintageCool 10y agoA few months ago I was developing for a breaking change and realized that I wasn't committing anything. That's very much an SVN mindset where merging is so painful that you culturally just avoid it altogether. Git's emphasis on being distributed and branching and merging constantly meant that, once I pulled my head out of my ass and started committing locally, I was able to enjoy the benefits of source control while developing my breaking changes without affecting anyone. And later, when I merged my branch into the master, it turned out to be completely painless.